Triple
T24741879
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Virginia segment of Capital Beltway |
E618584
|
entity |
| Predicate | hasHOVorHOTLanes |
P104384
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Virginia segment of Capital Beltway, hasHOVorHOTLanes, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHOVorHOTLanes Context triple: [Virginia segment of Capital Beltway, hasHOVorHOTLanes, yes]
-
A.
hasExpressLanes
Indicates that a roadway or transportation facility includes designated express lanes for faster or prioritized travel.
-
B.
hasHighOccupancyTollLanes
Indicates that a roadway or highway segment includes high-occupancy toll (HOT) lanes where vehicles meeting certain occupancy or payment conditions are allowed to travel.
-
C.
hasCarpoolLanes
chosen
Indicates that a road, route, or transportation facility includes designated carpool (high-occupancy vehicle) lanes available for use.
-
D.
hasDedicatedLanes
Indicates that specific lanes within a route or roadway are reserved exclusively for a particular type of traffic or use.
-
E.
hasLanes
Indicates that an entity, such as a road or pathway, is divided into one or more distinct lanes for traffic or movement.
- 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_69e2fab8f95c81908bb9e552cf3280c2 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f410a25ab88190a72db43043c1f6ff |
completed | May 1, 2026, 2:32 a.m. |
| PD | Predicate disambiguation | batch_69f40ef612c88190ab2f3f08d4a92018 |
completed | May 1, 2026, 2:24 a.m. |
Created at: April 18, 2026, 4:16 a.m.