Triple
T37434016
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The 606 |
E930217
|
entity |
| Predicate | followsFormerInfrastructure |
P14629
|
FINISHED |
| Object | Bloomingdale Line |
—
|
NE NERFINISHED |
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: Bloomingdale Line | Statement: [The 606, followsFormerInfrastructure, Bloomingdale Line]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: followsFormerInfrastructure Context triple: [The 606, followsFormerInfrastructure, Bloomingdale Line]
-
A.
formerInfrastructure
Indicates that an entity once served as infrastructure for another entity or system but no longer holds that functional status.
-
B.
formerTransportInfrastructure
Indicates that an entity was once used as transport infrastructure but no longer serves that function.
-
C.
followsFormerRailroad
chosen
Indicates that something is aligned with or traces the route of a former railroad line.
-
D.
predecessorInfrastructureOwner
Indicates that one infrastructure owner previously held ownership or responsibility before another in a temporal succession.
-
E.
usedInfrastructurePreviouslyOperatedBy
Indicates that an entity makes use of infrastructure that was formerly operated or managed by another entity.
- 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_69f76ebfdcb8819098562ff3db673b04 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ff70ecc1a481909571b18d56d982b8 |
completed | May 9, 2026, 5:37 p.m. |
| PD | Predicate disambiguation | batch_69ff70322a3c8190837840ea42cd3093 |
completed | May 9, 2026, 5:34 p.m. |
Created at: May 3, 2026, 4:17 p.m.