Triple
T759114
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brunswick Line |
E16025
|
entity |
| Predicate | usesRoute |
P2127
|
FINISHED |
| Object | former Baltimore and Ohio Railroad main line |
—
|
LITERAL 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: former Baltimore and Ohio Railroad main line | Statement: [Brunswick Line, usesRoute, former Baltimore and Ohio Railroad main line]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesRoute Context triple: [Brunswick Line, usesRoute, former Baltimore and Ohio Railroad main line]
-
A.
followsRouteOf
chosen
Indicates that one entity travels along the same path or route that another entity takes or has taken.
-
B.
usedToNavigate
Indicates that one entity served as a means or tool for another entity to find or follow a route or direction.
-
C.
isPartOfRoute
Indicates that something (such as a segment, stop, or step) belongs to and is contained within a larger route.
-
D.
avoidsRoute
Indicates that an entity deliberately does not use or travel along a particular route.
-
E.
usesTransport
Indicates that an entity employs or relies on a particular mode or means of transportation to move from one place to another.
- F. None of above.
Provenance (3 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_69a493684ee48190bd43b7c78da4aec8 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a67f9778819098d3c144dd26b976 |
completed | March 1, 2026, 8:50 p.m. |
| PD | Predicate disambiguation | batch_69a4a50348088190873a1446db657a78 |
completed | March 1, 2026, 8:43 p.m. |
Created at: March 1, 2026, 7:37 p.m.