Triple

T3693819
Position Surface form Disambiguated ID Type / Status
Subject Chappaquiddick Road network E78405 entity
Predicate hasTrafficRegime P49787 FINISHED
Object low speed limits 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: low speed limits | Statement: [Chappaquiddick Road network, hasTrafficRegime, low speed limits]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasTrafficRegime
Context triple: [Chappaquiddick Road network, hasTrafficRegime, low speed limits]
  • A. hasTrafficControl
    Indicates that some form of traffic management or regulation mechanism is present or applied to a given route, intersection, or transportation element.
  • B. hasTrafficPattern
    Indicates that there is a characteristic or recurring flow of traffic associated with an entity, such as its typical volume, direction, or timing of movement.
  • C. hasTrafficDirection
    Indicates that there is a specified flow or orientation of traffic associated with an entity (such as a road, lane, or route).
  • D. hasTrafficFunction
    Indicates that an entity performs, supports, or is assigned a specific function or role related to traffic management or control.
  • E. hasTrafficManagement
    Indicates that an entity implements, uses, or is associated with systems or measures for controlling and optimizing traffic flow.
  • F. None of above. chosen

Provenance (4 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_69ad85e3b1888190abc983e06968696d completed March 8, 2026, 2:21 p.m.
NER Named-entity recognition batch_69adc4e9e4748190aa178692ef27e3a6 completed March 8, 2026, 6:50 p.m.
PD Predicate disambiguation batch_69adb84dc5808190850aa6975cb09e27 completed March 8, 2026, 5:56 p.m.
PDg Predicate description generation batch_69adb902e61c81908f10494f828e260f completed March 8, 2026, 5:59 p.m.
Created at: March 8, 2026, 3:26 p.m.