Triple
T9334517
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Dark Hedges |
E224610
|
entity |
| Predicate | roadTrafficPolicy |
P29930
|
FINISHED |
| Object | banned through-traffic for most vehicles |
—
|
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: banned through-traffic for most vehicles | Statement: [The Dark Hedges, roadTrafficPolicy, banned through-traffic for most vehicles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roadTrafficPolicy Context triple: [The Dark Hedges, roadTrafficPolicy, banned through-traffic for most vehicles]
-
A.
roadTraffic
Indicates the presence, flow, or conditions of vehicles and movement along roads or streets.
-
B.
roadTrafficRuleJurisdiction
Indicates the jurisdiction or authority under whose road traffic rules a given situation, entity, or action is governed.
-
C.
trafficRestriction
chosen
Indicates a limitation or prohibition on the movement or flow of traffic between entities, such as vehicles, routes, or areas.
-
D.
trafficManagementStrategy
Indicates a method or plan used to control, organize, or optimize the flow of traffic within a transportation system.
-
E.
servesGovernmentTraffic
Indicates that an entity provides services or functionality specifically for government-related network or data traffic.
- 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_69ca84286fcc81909f6e7fd7a7e862a2 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd37ee53988190bcc76588edbc2858 |
completed | April 1, 2026, 3:21 p.m. |
| PD | Predicate disambiguation | batch_69cc7a643924819097f01144734901cf |
completed | April 1, 2026, 1:52 a.m. |
Created at: March 30, 2026, 7:39 p.m.