Triple
T17608477
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CTA Route 201 Central/Ridge |
E428899
|
entity |
| Predicate | primaryStreetsServed |
P46518
|
FINISHED |
| Object | Central Street |
—
|
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: Central Street | Statement: [CTA Route 201 Central/Ridge, primaryStreetsServed, Central Street]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryStreetsServed Context triple: [CTA Route 201 Central/Ridge, primaryStreetsServed, Central Street]
-
A.
roadServed
Indicates that a road is provided with necessary services or infrastructure support by a responsible entity.
-
B.
primaryCorridorServed
chosen
Indicates that a corridor is the main route or pathway served by a given service, facility, or entity.
-
C.
roadNetworkServedBy
Indicates that a particular road network is provided, maintained, or operated by a specified service, organization, or infrastructure system.
-
D.
isPrimarySurfaceStreetIn
Indicates that a street serves as a main or primary surface-level roadway within a specified area or jurisdiction.
-
E.
hasNumberOfStreets
Indicates the relationship that specifies how many streets are associated with or contained within a given entity.
- 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_69d889e1c6148190ba76241e74688f8b |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e46c4d8374819097cb112fba405e77 |
completed | April 19, 2026, 5:46 a.m. |
| PD | Predicate disambiguation | batch_69e3cdd7da34819099bc9481c5a79bab |
completed | April 18, 2026, 6:30 p.m. |
Created at: April 10, 2026, 5:51 a.m.