Triple
T37941148
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North Dakota state highway system |
E946488
|
entity |
| Predicate | trafficRegulationBy |
P7767
|
FINISHED |
| Object | North Dakota traffic laws |
—
|
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: North Dakota traffic laws | Statement: [North Dakota state highway system, trafficRegulationBy, North Dakota traffic laws]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: trafficRegulationBy Context triple: [North Dakota state highway system, trafficRegulationBy, North Dakota traffic laws]
-
A.
roadTrafficRuleJurisdiction
chosen
Indicates the jurisdiction or authority under whose road traffic rules a given situation, entity, or action is governed.
-
B.
navigationRegulation
Indicates rules or constraints that govern how navigation or movement is allowed, restricted, or managed within a particular space or system.
-
C.
trafficRestriction
Indicates a limitation or prohibition on the movement or flow of traffic between entities, such as vehicles, routes, or areas.
-
D.
hasTrafficRegime
Indicates that a specified traffic control or regulatory system applies to a given road, area, or transport context.
-
E.
roadTraffic
Indicates the presence, flow, or conditions of vehicles and movement along roads or streets.
- 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_69f76ef531ac8190ae6d99e5786e76ec |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fbc7b78f9481909f4f8fc2e3fdcde1 |
completed | May 6, 2026, 10:59 p.m. |
| PD | Predicate disambiguation | batch_69fbbd18c9908190928d274f8731dfa8 |
completed | May 6, 2026, 10:13 p.m. |
Created at: May 3, 2026, 4:20 p.m.