Triple
T7697182
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Loop 1 (Mopac Expressway) |
E174398
|
entity |
| Predicate | tollComponent |
P78341
|
FINISHED |
| Object | managed express lanes |
—
|
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: managed express lanes | Statement: [Loop 1 (Mopac Expressway), tollComponent, managed express lanes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tollComponent Context triple: [Loop 1 (Mopac Expressway), tollComponent, managed express lanes]
-
A.
tollIntroduced
Indicates that a toll was established or put into effect for using a particular route, facility, or service.
-
B.
tollingType
Indicates the specific method or basis by which a toll, fee, or charge is applied or calculated in a given context.
-
C.
tollDevice
Indicates a device is used to collect or process tolls for passage on a road, bridge, or similar infrastructure.
-
D.
appliesTollTo
Indicates that a fee or charge is imposed on a subject for using, accessing, or passing through something.
-
E.
tollBridge
Indicates that passage across a bridge requires payment of a toll or fee.
- F. None of above. chosen
Provenance (4 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_69c6995a72cc8190998e56daa6f8e453 |
completed | March 27, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69c70402169481909b219dc5f4a64b9b |
completed | March 27, 2026, 10:26 p.m. |
| PD | Predicate disambiguation | batch_69c70165e78c8190bf6b3c34e243cb81 |
completed | March 27, 2026, 10:15 p.m. |
| PDg | Predicate description generation | batch_69c7040091608190a9e46ecfb2ff0bca |
completed | March 27, 2026, 10:26 p.m. |
Created at: March 27, 2026, 4:03 p.m.