Triple

T12993353
Position Surface form Disambiguated ID Type / Status
Subject Vinkel, Netherlands E321969 entity
Predicate hasRoadTrafficRegulation P7767 FINISHED
Object European Union road standards 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: European Union road standards | Statement: [Vinkel, Netherlands, hasRoadTrafficRegulation, European Union road standards]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasRoadTrafficRegulation
Context triple: [Vinkel, Netherlands, hasRoadTrafficRegulation, European Union road standards]
  • A. hasTrafficRegime
    Indicates that a specified traffic control or regulatory system applies to a given road, area, or transport context.
  • B. hasTrafficControl
    Indicates that some form of traffic management or regulation mechanism is present or applied to a given route, intersection, or transportation element.
  • C. hasRoadSign
    Indicates that one entity possesses, displays, or is associated with a particular road sign.
  • D. roadTrafficRuleJurisdiction chosen
    Indicates the jurisdiction or authority under whose road traffic rules a given situation, entity, or action is governed.
  • E. hasTrafficSignals
    Indicates that traffic control signals are present at or associated with a given location or roadway feature.
  • 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_69d8076479b8819090afce3591939cdf completed April 9, 2026, 8:09 p.m.
NER Named-entity recognition batch_69d97f2a71a0819098bb6cf8a4b2208a completed April 10, 2026, 10:52 p.m.
PD Predicate disambiguation batch_69d97dbdd94c8190ac4bbecca02dc77b completed April 10, 2026, 10:46 p.m.
Created at: April 9, 2026, 8:44 p.m.