Triple
T687971
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | I-66 Express Lanes Outside the Beltway |
E13325
|
entity |
| Predicate | usesTollSystem |
P3913
|
FINISHED |
| Object | all-electronic tolling |
—
|
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: all-electronic tolling | Statement: [I-66 Express Lanes Outside the Beltway, usesTollSystem, all-electronic tolling]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesTollSystem Context triple: [I-66 Express Lanes Outside the Beltway, usesTollSystem, all-electronic tolling]
-
A.
hasToll
Indicates that the use, access, or passage associated with something requires payment of a toll or fee.
-
B.
tollingType
chosen
Indicates the specific method or basis by which a toll, fee, or charge is applied or calculated in a given context.
-
C.
hasTollSegment
Indicates that a route, road, or path includes a segment where a toll must be paid.
-
D.
fareSystem
Indicates a relationship where a system is used to determine, collect, or manage fares or payments for transportation or similar services.
-
E.
hasCharge
Indicates that an entity possesses a specific electrical or formal charge, such as positive, negative, or neutral.
- 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_69a4933e0f98819097d22766c49b61b8 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a4a0f55f7481909e052a25bd12d455 |
completed | March 1, 2026, 8:26 p.m. |
| PD | Predicate disambiguation | batch_69a49d2048d48190ab99ab59accb6909 |
completed | March 1, 2026, 8:10 p.m. |
Created at: March 1, 2026, 7:36 p.m.