Triple
T28952278
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eastchester |
E731048
|
entity |
| Predicate | nearbySubwayTerminal |
P26735
|
FINISHED |
| Object | Eastchester–Dyre Avenue station |
—
|
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: Eastchester–Dyre Avenue station | Statement: [Eastchester, nearbySubwayTerminal, Eastchester–Dyre Avenue station]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearbySubwayTerminal Context triple: [Eastchester, nearbySubwayTerminal, Eastchester–Dyre Avenue station]
-
A.
subwayServiceAtNearbyStation
Indicates that there is subway service available at a station located near the referenced place or entity.
-
B.
nearestSuburbanRailwayStation
Indicates the relationship where a given place is associated with the suburban railway station that is geographically closest to it.
-
C.
nearestUndergroundStation
chosen
Indicates the relationship where a specific underground (subway/metro) station is the closest one in distance to a given location or entity.
-
D.
nearbyTerminus
Indicates that one terminus (end point or final stop) is located close to another terminus in space.
-
E.
nearestRailwayTerminus
Indicates that one location is the closest railway terminus to another specified place.
- 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_69f043eb9bcc819091ac7b07aecb6475 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69fb6fdc7eb081908ab8475efb38c430 |
completed | May 6, 2026, 4:44 p.m. |
| PD | Predicate disambiguation | batch_69fb5a986e588190b7a10892bd2ff44c |
completed | May 6, 2026, 3:13 p.m. |
Created at: April 28, 2026, 8:44 a.m.