Triple

T37758082
Position Surface form Disambiguated ID Type / Status
Subject Interstate 35 in Austin, Texas E941175 entity
Predicate frontageRoadConfiguration P138133 FINISHED
Object one-way frontage roads 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: one-way frontage roads | Statement: [Interstate 35 in Austin, Texas, frontageRoadConfiguration, one-way frontage roads]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: frontageRoadConfiguration
Context triple: [Interstate 35 in Austin, Texas, frontageRoadConfiguration, one-way frontage roads]
  • A. hasFrontageRoads chosen
    Indicates that a primary road or highway is accompanied by one or more adjacent frontage roads running alongside it.
  • B. streetFrontageOn
    Indicates that a property or parcel directly borders or faces a particular street along at least one of its sides.
  • C. hasRoadConfiguration
    Indicates that there exists a specific arrangement or layout of roads associated with or characterizing an entity.
  • D. hasStreetFront
    Indicates that one entity directly borders or faces onto a particular street along its frontage.
  • E. hasSideStreetType
    Indicates that an entity (such as a street or road segment) is associated with a specific type or classification of side street.
  • 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_69f76ee1f3a88190834e6c8af99bccc9 completed May 3, 2026, 3:50 p.m.
NER Named-entity recognition batch_69fbb9e8108c8190ae1c7940b1677e95 completed May 6, 2026, 10 p.m.
PD Predicate disambiguation batch_69fbb141605c8190b9c27d70352522db completed May 6, 2026, 9:23 p.m.
Created at: May 3, 2026, 4:19 p.m.