Triple
T28132523
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chicago–Indianapolis corridor |
E711102
|
entity |
| Predicate | connectsCityInState |
P25797
|
FINISHED |
| Object | Chicago, Illinois |
—
|
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: Chicago, Illinois | Statement: [Chicago–Indianapolis corridor, connectsCityInState, Chicago, Illinois]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: connectsCityInState Context triple: [Chicago–Indianapolis corridor, connectsCityInState, Chicago, Illinois]
-
A.
connectsMajorCityState
Indicates that something serves as a link or route between a major city and the state it belongs to.
-
B.
connectsCity
Indicates a relationship where one entity serves as a link or route that joins or provides direct access between two cities.
-
C.
associatedCityState
chosen
Indicates a relationship where a city is linked to the state with which it is formally or contextually connected.
-
D.
stateCapitalConnection
Indicates a relationship where one entity is the capital city of a given state or is otherwise connected to that state in its role as capital.
-
E.
connectsCityTo
Indicates a relationship in which a route, infrastructure, or link joins one city to another, enabling connection or interaction between them.
- 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_69ef9b73bd288190a21ae3d6aa14f386 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69fd3a69f1e08190a11aed015bff0858 |
completed | May 8, 2026, 1:20 a.m. |
| PD | Predicate disambiguation | batch_69fd39124180819080ca7911d3515d6d |
completed | May 8, 2026, 1:14 a.m. |
Created at: April 27, 2026, 9:24 p.m.