Triple

T16533418
Position Surface form Disambiguated ID Type / Status
Subject Intercounty Connector (MD 200) E401623 entity
Predicate highwayNumberingSystem P123928 FINISHED
Object Maryland state highway system 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: Maryland state highway system | Statement: [Intercounty Connector (MD 200), highwayNumberingSystem, Maryland state highway system]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: highwayNumberingSystem
Context triple: [Intercounty Connector (MD 200), highwayNumberingSystem, Maryland state highway system]
  • A. UShighwayNumber
    Indicates that a U.S. highway is identified by a specific route number.
  • B. nationalHighwayNetworkState
    Indicates that a state is part of, or associated with, the national highway network.
  • C. isNumberedHighway
    Indicates that a roadway is officially designated and signed as a numbered highway within a road network.
  • D. primaryInterstateHighway
    Indicates that the subject is designated as a primary (main) interstate highway within the interstate highway system.
  • E. nationalHighwayConnectivity
    Indicates the extent to which locations are linked by a network of national highways enabling direct or efficient road travel between them.
  • 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_69d883838abc8190bc79cb2d41733ce2 completed April 10, 2026, 4:58 a.m.
NER Named-entity recognition batch_69e32ed97b0881909de106418aca8180 completed April 18, 2026, 7:12 a.m.
PD Predicate disambiguation batch_69e2969fab208190ad64164d24748c45 completed April 17, 2026, 8:22 p.m.
PDg Predicate description generation batch_69e2d7f97e548190a474691a152bd8e8 completed April 18, 2026, 1:01 a.m.
Created at: April 10, 2026, 5:15 a.m.