Triple
T2807692
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Northgate |
E54092
|
entity |
| Predicate | lightRailRole |
P14634
|
FINISHED |
| Object | northern terminus of a Link light rail line |
—
|
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 terminus of a Link light rail line | Statement: [Northgate, lightRailRole, northern terminus of a Link light rail line]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lightRailRole Context triple: [Northgate, lightRailRole, northern terminus of a Link light rail line]
-
A.
hasLightRailSystem
Indicates that a place possesses and operates a light rail transit system.
-
B.
railwayLineRole
chosen
Indicates the specific functional role or purpose that a railway line serves within a rail network or transportation system.
-
C.
railNetworkRole
Indicates the specific function or responsibility an entity has within a rail network system.
-
D.
transportationRole
Indicates a role or function that an entity has specifically in the context of providing, operating, or supporting transportation.
-
E.
hasPublicTransitRole
Indicates that an entity holds a specific functional role or responsibility within a public transit system.
- 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_69ab49dcee188190b5c6eca9ae9e3469 |
completed | March 6, 2026, 9:40 p.m. |
| NER | Named-entity recognition | batch_69abde2ec2ac8190bd702ad3eafb6aed |
completed | March 7, 2026, 8:13 a.m. |
| PD | Predicate disambiguation | batch_69abdd059f308190853191f6ffe2bc6f |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 9:59 p.m.