Triple
T30796089
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BR |
E784231
|
entity |
| Predicate | associatedRailLine |
P848
|
FINISHED |
| Object | Lakeshore West line |
E296488
|
NE FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Lakeshore West line | Statement: [BR, associatedRailLine, Lakeshore West line]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedRailLine Context triple: [BR, associatedRailLine, Lakeshore West line]
-
A.
railroadLineServed
Indicates that a particular railroad line provides service to, or operates through, a given location or facility.
-
B.
relatedRailroad
Indicates that there is an association or connection between an entity and a specific railroad, such as ownership, operation, service, or historical linkage.
-
C.
railwayLine
chosen
Indicates that there is a railway line connection or route associated with or passing through the referenced entity.
-
D.
amtrakLine
Indicates that one entity is an Amtrak-operated rail line serving or connecting the other entity.
-
E.
servesAsRailheadFor
Indicates that one location functions as the primary loading, unloading, or distribution point on a railway network for another area or operation.
- F. None of above.
Provenance (4 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69f224b2e2a48190b19aa43db9da5b67 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a28fb9941f081909002bcd2ced66753 |
completed | June 10, 2026, 5:52 a.m. |
| PD | Predicate disambiguation | batch_6a0379e2fac0819089b522db3260028c |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 29, 2026, 8:42 p.m.