Triple

T1999460
Position Surface form Disambiguated ID Type / Status
Subject M6 motorway (near Wigan) E43431 entity
Predicate hasCarriageway P22311 FINISHED
Object dual carriageway 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: dual carriageway | Statement: [M6 motorway (near Wigan), hasCarriageway, dual carriageway]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasCarriageway
Context triple: [M6 motorway (near Wigan), hasCarriageway, dual carriageway]
  • A. hasCarriagewayType chosen
    Indicates the specific structural or functional type of carriageway associated with a road segment (e.g., single, dual, or other carriageway configurations).
  • B. roadwayCarries
    Indicates that a roadway serves as a route that supports or conveys a particular transportation facility, traffic flow, or designated use.
  • C. hasLanes
    Indicates that an entity, such as a road or pathway, is divided into one or more distinct lanes for traffic or movement.
  • D. hasWheelchairLanes
    Indicates that a location, route, or facility includes designated lanes or pathways specifically designed for wheelchair use.
  • E. hasDedicatedLanes
    Indicates that specific lanes within a route or roadway are reserved exclusively for a particular type of traffic or use.
  • 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_69a88715dbbc8190b2299e29e955d997 completed March 4, 2026, 7:25 p.m.
NER Named-entity recognition batch_69abb91055d88190a980e7b42e5895d4 completed March 7, 2026, 5:35 a.m.
PD Predicate disambiguation batch_69abb79c97d48190b3147430ed39faa9 completed March 7, 2026, 5:29 a.m.
Created at: March 4, 2026, 7:37 p.m.