Triple

T5032424
Position Surface form Disambiguated ID Type / Status
Subject Capital Beltway region E113336 entity
Predicate hasInfrastructureFeature P182 FINISHED
Object radial highways connecting to I-495 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: radial highways connecting to I-495 | Statement: [Capital Beltway region, hasInfrastructureFeature, radial highways connecting to I-495]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasInfrastructureFeature
Context triple: [Capital Beltway region, hasInfrastructureFeature, radial highways connecting to I-495]
  • A. hasFeature chosen
    Indicates that an entity possesses, exhibits, or includes a particular characteristic, attribute, or component.
  • B. hasInfrastructureType
    Indicates that an entity possesses or is associated with a specific category or type of infrastructure.
  • C. supportsFeature
    Indicates that one entity provides, enables, or is compatible with a particular feature or capability of another.
  • D. hasFeatureCode
    Indicates that an entity is associated with a specific feature identifier or code that characterizes one of its properties or attributes.
  • E. hasGlobalInfrastructure
    Indicates that an entity possesses infrastructure, facilities, or operational capabilities that are distributed across multiple countries or regions worldwide.
  • 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_69bd443775e48190a646ffbfc4334723 completed March 20, 2026, 12:57 p.m.
NER Named-entity recognition batch_69bd73b4d1708190aa1fa63104555f8a completed March 20, 2026, 4:20 p.m.
PD Predicate disambiguation batch_69bd71509e9c8190a60c1d8d04936a12 completed March 20, 2026, 4:09 p.m.
Created at: March 20, 2026, 1:36 p.m.