Triple
T28372389
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IRT elevated network |
E718666
|
entity |
| Predicate | hadStations |
P83367
|
FINISHED |
| Object | elevated railway stations |
—
|
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: elevated railway stations | Statement: [IRT elevated network, hadStations, elevated railway stations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadStations Context triple: [IRT elevated network, hadStations, elevated railway stations]
-
A.
hasStations
chosen
Indicates that one entity possesses, contains, or is associated with one or more stations.
-
B.
hasFormerStation
Indicates that an entity previously had a particular station (e.g., a stop, depot, or facility) that is no longer in active use or part of its current infrastructure.
-
C.
hasStationAt
Indicates that an entity maintains or operates a station located at a specified place.
-
D.
hasDedicatedStations
Indicates that specific stations are exclusively assigned or reserved for a particular entity or purpose.
-
E.
hasFocalStations
Indicates that an entity is associated with one or more primary or central stations that serve as its main points of focus or operation.
- 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_69eff6ee5afc8190bd7375a29f0cc6c6 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f64e37f7fc819083809149b6661e3c |
completed | May 2, 2026, 7:19 p.m. |
| PD | Predicate disambiguation | batch_69f64caede108190a35cc7cbfead866f |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 28, 2026, 1 a.m.