Triple
T27510754
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Castle Hill |
E694403
|
entity |
| Predicate | nearestSubwayLine |
P33788
|
FINISHED |
| Object | IRT Pelham 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: IRT Pelham Line | Statement: [Castle Hill, nearestSubwayLine, IRT Pelham Line]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearestSubwayLine Context triple: [Castle Hill, nearestSubwayLine, IRT Pelham Line]
-
A.
nearestCommuterRailLine
Indicates the commuter rail line that is geographically closest to a given location or entity.
-
B.
nearestRailwayLine
Indicates that one railway line is the closest in distance to a given location or feature compared to all other railway lines.
-
C.
nearUndergroundLine
chosen
Indicates that one entity is located close in distance to an underground (subway/metro) line.
-
D.
nearestUndergroundStation
Indicates the relationship where a specific underground (subway/metro) station is the closest one in distance to a given location or entity.
-
E.
nearestSuburbanRailwayStation
Indicates the relationship where a given place is associated with the suburban railway station that is geographically closest to it.
- 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_69ef53842afc8190ba6bd4e4999bda67 |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f68805b4848190b75da14996d52a38 |
completed | May 2, 2026, 11:25 p.m. |
| PD | Predicate disambiguation | batch_69f68609c0b08190a8e1238a4d97c270 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 27, 2026, 1:16 p.m.