Triple
T24753904
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 157th Street |
E619224
|
entity |
| Predicate | southboundNextStation |
P48849
|
FINISHED |
| Object | 145th Street |
—
|
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: 145th Street | Statement: [157th Street, southboundNextStation, 145th Street]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: southboundNextStation Context triple: [157th Street, southboundNextStation, 145th Street]
-
A.
nextStationOnLine1Southbound
chosen
Indicates that one station is the immediate next stop when traveling southbound on transit line 1.
-
B.
nextStationEast
Indicates that one station is the immediate next station to the east of another station along a route or line.
-
C.
adjacentStationSouth
Indicates that one station is directly to the south of another station, with no other station in between.
-
D.
distanceToNextStationSouth
Indicates the measured distance from a given point or station to the next station located to its south.
-
E.
adjacentStationTowardsSouth
Indicates that one station is directly next to another in the southward direction along a route or line.
- 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_69e2fabb349881908a13a212a0221a63 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f410a25ab88190a72db43043c1f6ff |
completed | May 1, 2026, 2:32 a.m. |
| PD | Predicate disambiguation | batch_69f40ef612c88190ab2f3f08d4a92018 |
completed | May 1, 2026, 2:24 a.m. |
Created at: April 18, 2026, 4:25 a.m.