Triple

T594377
Position Surface form Disambiguated ID Type / Status
Subject Interstate Highway System E17346 entity
Predicate auxiliaryRouteType P6117 FINISHED
Object beltway 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: beltway | Statement: [Interstate Highway System, auxiliaryRouteType, beltway]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: auxiliaryRouteType
Context triple: [Interstate Highway System, auxiliaryRouteType, beltway]
  • A. auxiliaryRoutePattern chosen
    Indicates that one route serves as an auxiliary or supplemental path that follows or branches from a primary route according to a specific pattern or configuration.
  • B. hasTransportRoute
    Indicates that there exists a designated transportation connection or route linking one entity to another.
  • C. guidewayType
    Indicates the specific kind or classification of guideway used in a transportation or movement system.
  • D. parentRouteType
    Indicates that one route type serves as the parent or higher-level category for another route type within a route hierarchy.
  • E. significantlyShortensRouteBetween
    Indicates that one entity provides a connection between two others that makes the path or travel distance between them substantially shorter than alternative routes.
  • 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_69a49379d09c8190ac7e00b24e2810b1 completed March 1, 2026, 7:28 p.m.
NER Named-entity recognition batch_69a49bd15c5881909b59ed4c88687e7b completed March 1, 2026, 8:04 p.m.
PD Predicate disambiguation batch_69a494ceeb7881909a91ed1a35d5bf0a completed March 1, 2026, 7:34 p.m.
Created at: March 1, 2026, 7:33 p.m.