Triple
T8943920
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Woodlawn station (IRT Jerome Avenue Line) |
E212970
|
entity |
| Predicate | hasNorthTerminalYard |
P18851
|
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: [Woodlawn station (IRT Jerome Avenue Line), hasNorthTerminalYard, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNorthTerminalYard Context triple: [Woodlawn station (IRT Jerome Avenue Line), hasNorthTerminalYard, yes]
-
A.
hasRailYard
chosen
Indicates that one entity possesses, contains, or includes a rail yard as part of its facilities or infrastructure.
-
B.
terminusNorth
Indicates that one entity serves as the northern endpoint or final stop of another entity, such as a route, line, or path.
-
C.
northernTerminusConnects
Indicates that a route, line, or pathway connects to or ends at a specified location at its northernmost terminus.
-
D.
hasRailFacility
Indicates that an entity possesses or is served by a rail-related facility, such as a railway station, terminal, or yard.
-
E.
hasCargoTerminal
Indicates that a location or facility includes or is equipped with a cargo terminal for handling freight.
- 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_69ca839694c88190b324ffeb43d23b08 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc66da71808190b4454b2f95aae0bd |
completed | April 1, 2026, 12:29 a.m. |
| PD | Predicate disambiguation | batch_69cc5ed5267c8190a43feb2a2f3df1ec |
completed | March 31, 2026, 11:55 p.m. |
Created at: March 30, 2026, 6:59 p.m.