Triple
T666206
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | I-66 Express Lanes Inside the Beltway |
E12866
|
entity |
| Predicate | trafficManagementStrategy |
P17413
|
FINISHED |
| Object | managed lanes program |
—
|
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 lanes program | Statement: [I-66 Express Lanes Inside the Beltway, trafficManagementStrategy, managed lanes program]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: trafficManagementStrategy Context triple: [I-66 Express Lanes Inside the Beltway, trafficManagementStrategy, managed lanes program]
-
A.
trafficDirection
Indicates the direction in which traffic is intended or allowed to move relative to a given reference point or segment.
-
B.
hasTrafficDirection
Indicates that there is a specified flow or orientation of traffic associated with an entity (such as a road, lane, or route).
-
C.
trafficLevel
Indicates the degree of congestion or flow intensity present in a transportation network or route at a given time.
-
D.
trafficSeparation
Indicates a relationship where movement or flow is organized into distinct, non-overlapping paths or zones to prevent interference or collisions.
-
E.
trafficType
Indicates the category or nature of traffic involved in a given interaction, flow, or connection (e.g., type of network, data, or transport traffic).
- 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_69a493355dec819098d4244b2fa34885 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a49fd4f4988190a0973ceb7329b4c9 |
completed | March 1, 2026, 8:21 p.m. |
| PD | Predicate disambiguation | batch_69a49d16cff881908c8d2c3fe4d1d6fb |
completed | March 1, 2026, 8:09 p.m. |
| PDg | Predicate description generation | batch_69a49df19c9481909cc9bc33ed7f011b |
completed | March 1, 2026, 8:13 p.m. |
Created at: March 1, 2026, 7:36 p.m.