Triple
T36762353
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Edgware Underground Station |
E908236
|
entity |
| Predicate | hasRailwayTerminusRole |
P21210
|
FINISHED |
| Object | Northern line terminus |
—
|
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: Northern line terminus | Statement: [Edgware Underground Station, hasRailwayTerminusRole, Northern line terminus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRailwayTerminusRole Context triple: [Edgware Underground Station, hasRailwayTerminusRole, Northern line terminus]
-
A.
hasRailwayStationRole
Indicates that an entity holds or is assigned a specific functional role or capacity within the operation or management of a railway station.
-
B.
railroadTerminusFor
chosen
Indicates that one location serves as the end point or final station of a particular railroad line for another location.
-
C.
hasRailStation
Indicates that one entity possesses, contains, or is served by a rail station.
-
D.
hasRailwayStation
Indicates that a place or location is served by, or contains, a railway station.
-
E.
isRailwayStation
Indicates that the subject is a railway station, i.e., a facility where trains regularly stop to pick up or drop off passengers and/or 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_69f76e786ba481909cdcf6cf6b39dd32 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fd974d75e08190af46b1d608769f3b |
completed | May 8, 2026, 7:57 a.m. |
| PD | Predicate disambiguation | batch_69fd94ff792c8190bedf4a639d3da809 |
completed | May 8, 2026, 7:47 a.m. |
Created at: May 3, 2026, 4:12 p.m.