Triple

T1511946
Position Surface form Disambiguated ID Type / Status
Subject Forth Road Bridge E32031 entity
Predicate trafficRestriction P29930 FINISHED
Object no general heavy goods 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: no general heavy goods vehicles | Statement: [Forth Road Bridge, trafficRestriction, no general heavy goods vehicles]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: trafficRestriction
Context triple: [Forth Road Bridge, trafficRestriction, no general heavy goods vehicles]
  • A. trafficDirection
    Indicates the direction in which traffic is intended or allowed to move relative to a given reference point or segment.
  • B. pedestrianRestrictions
    Indicates that there are specific rules or limitations governing where or how pedestrians may travel or access an area.
  • C. regulatesTrafficBetween
    Indicates that one entity controls, manages, or directs the flow of traffic occurring between two other entities or locations.
  • D. trafficManagementStrategy
    Indicates a method or plan used to control, organize, or optimize the flow of traffic within a transportation system.
  • E. hasTrafficDirection
    Indicates that there is a specified flow or orientation of traffic associated with an entity (such as a road, lane, or route).
  • 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_69a885e8caf88190a5fbb6159ce87786 completed March 4, 2026, 7:20 p.m.
NER Named-entity recognition batch_69a9396e16408190b5e7b0ac43376d81 completed March 5, 2026, 8:06 a.m.
PD Predicate disambiguation batch_69a907aa67cc81909f00135365447399 completed March 5, 2026, 4:33 a.m.
PDg Predicate description generation batch_69a9396d3e1081909aa269b42041c357 completed March 5, 2026, 8:06 a.m.
Created at: March 4, 2026, 7:26 p.m.