Triple

T20550797
Position Surface form Disambiguated ID Type / Status
Subject Missouri lettered route system E504590 entity
Predicate typicalTrafficVolume P56035 FINISHED
Object lower than primary state highways 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: lower than primary state highways | Statement: [Missouri lettered route system, typicalTrafficVolume, lower than primary state highways]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: typicalTrafficVolume
Context triple: [Missouri lettered route system, typicalTrafficVolume, lower than primary state highways]
  • A. trafficDirection
    Indicates the direction in which traffic is intended or allowed to move relative to a given reference point or segment.
  • B. roadTraffic
    Indicates the presence, flow, or conditions of vehicles and movement along roads or streets.
  • C. cargoTrafficRank
    Indicates the relative position of an entity in an ordered list based on the volume or intensity of its cargo traffic.
  • D. annualTraffic
    Indicates the typical amount or volume of traffic associated with something over the course of a year.
  • E. relativeTrafficLevel chosen
    Indicates the comparative intensity or volume of traffic between two or more locations, routes, or time periods.
  • 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_69e0b4b52c048190952b4d0f430813a3 completed April 16, 2026, 10:06 a.m.
NER Named-entity recognition batch_69e6a5d8b55081909c3e3e972aff846d completed April 20, 2026, 10:16 p.m.
PD Predicate disambiguation batch_69e59fe5592c8190bb6122b784496d02 completed April 20, 2026, 3:39 a.m.
Created at: April 16, 2026, 11:38 a.m.