Triple
T16929636
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 10th Street Station |
E410669
|
entity |
| Predicate | isOnCorridor |
P1018
|
FINISHED |
| Object | Central Corridor |
E1093884
|
NE 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: Central Corridor | Statement: [10th Street Station, isOnCorridor, Central Corridor]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Central Corridor Context triple: [10th Street Station, isOnCorridor, Central Corridor]
-
A.
Central Corridor
chosen
Central Corridor is a major transit and development corridor in the Minneapolis–Saint Paul area that connects key neighborhoods, universities, and commercial districts.
-
B.
Blue Line
The Blue Line is one of the primary routes of the MetroLink light rail system serving the St. Louis metropolitan area.
-
C.
Blue Line
The Blue Line is one of the main rapid transit corridors of the Hyderabad Metro system in Hyderabad, India.
-
D.
Blue Line
The Blue Line is one of the primary light rail transit routes in Calgary's CTrain system, serving key corridors across the city.
-
E.
Blue Line
The Blue Line is a light rail service in Pittsburgh's public transit system that connects downtown with several southern suburbs.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d886c886688190967be07322597ac9 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3cf23873c8190bdc9121d6c3850e2 |
completed | April 18, 2026, 6:36 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a00cfdeb7a88190aac21a8645607dc8 |
completed | May 10, 2026, 6:35 p.m. |
Created at: April 10, 2026, 5:30 a.m.