Triple
T7635423
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Illinois Tollway |
E172865
|
entity |
| Predicate | typeOfTollRoads |
P1019
|
FINISHED |
| Object | interstate highways |
—
|
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: interstate highways | Statement: [Illinois Tollway, typeOfTollRoads, interstate highways]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfTollRoads Context triple: [Illinois Tollway, typeOfTollRoads, interstate highways]
-
A.
typeOfTollSystem
Indicates the specific kind or category of toll collection system used in a given context.
-
B.
hasTollBoothsAt
Indicates that toll booths are present at or associated with a particular location or segment of infrastructure.
-
C.
isTollFacilityOf
Indicates that a facility (such as a toll booth, plaza, or gantry) is part of, or used to collect tolls for, a specific toll road or toll transportation infrastructure.
-
D.
roadType
chosen
Indicates the classification or category of a road based on its functional or physical characteristics.
-
E.
tollingType
Indicates the specific method or basis by which a toll, fee, or charge is applied or calculated in a given context.
- 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_69c69952849881908fdcea7a93bfc307 |
completed | March 27, 2026, 2:50 p.m. |
| NER | Named-entity recognition | batch_69c6faa83fcc8190a3f0bb20cbe1b2d6 |
completed | March 27, 2026, 9:46 p.m. |
| PD | Predicate disambiguation | batch_69c6f4e8cadc8190b7977fcd213954dd |
completed | March 27, 2026, 9:21 p.m. |
Created at: March 27, 2026, 3:57 p.m.