Triple
T13730577
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Buffalo–Depew station |
E329785
|
entity |
| Predicate | isOnFreightCorridor |
P42526
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Buffalo–Depew station, isOnFreightCorridor, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isOnFreightCorridor Context triple: [Buffalo–Depew station, isOnFreightCorridor, yes]
-
A.
isOnFreightRoute
chosen
Indicates that something lies along or is included within a designated freight transportation route used for moving goods.
-
B.
locatedInTransportCorridor
Indicates that an entity is situated within a designated transport corridor used for the movement of people or goods.
-
C.
isCoastalCorridor
Indicates that a region or area functions as a continuous coastal passageway connecting different coastal locations.
-
D.
isOnEastWestTrunkLine
Indicates that something is located on, or directly aligned with, a primary east–west transportation or utility trunk line.
-
E.
isIndustrialCorridor
Indicates that an area or route is designated and used primarily for industrial activities, facilities, or transportation.
- 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_69d80772315881908f980cae40d91664 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69de01f92b588190be97ec4564dddd59 |
completed | April 14, 2026, 8:59 a.m. |
| PD | Predicate disambiguation | batch_69dbbe950b148190ba0df8a749269ec6 |
completed | April 12, 2026, 3:47 p.m. |
Created at: April 9, 2026, 9:55 p.m.