Triple
T19478536
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Loveland Pass |
E487316
|
entity |
| Predicate | roadRestriction |
P29930
|
FINISHED |
| Object | chain requirements during winter storms |
—
|
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: chain requirements during winter storms | Statement: [Loveland Pass, roadRestriction, chain requirements during winter storms]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roadRestriction Context triple: [Loveland Pass, roadRestriction, chain requirements during winter storms]
-
A.
trafficRestriction
chosen
Indicates a limitation or prohibition on the movement or flow of traffic between entities, such as vehicles, routes, or areas.
-
B.
roadClosedReason
Indicates the reason why a particular road is closed.
-
C.
roadAffected
Indicates that a road is impacted or disrupted by a condition, event, or action, such as construction, accidents, or adverse weather.
-
D.
roadControlled
Indicates that one entity has authority over, manages, or regulates the use and conditions of a particular road.
-
E.
isTrafficCalmed
Indicates that a road or street has measures in place to reduce vehicle speed and improve safety for users.
- 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_69d8e8d924388190b847cb15bb3d0aff |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e63437b9748190a8fc6bf6b3d90918 |
completed | April 20, 2026, 2:12 p.m. |
| PD | Predicate disambiguation | batch_69e4fd7883308190b73912a71a35a835 |
completed | April 19, 2026, 4:06 p.m. |
Created at: April 10, 2026, 1:39 p.m.