Triple

T34678806
Position Surface form Disambiguated ID Type / Status
Subject U.S. Route 31 E890564 entity
Predicate transportationRoleNear P96747 FINISHED
Object Tipton, Indiana NE NERFINISHED

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: Tipton, Indiana | Statement: [U.S. Route 31, transportationRoleNear, Tipton, Indiana]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: transportationRoleNear
Context triple: [U.S. Route 31, transportationRoleNear, Tipton, Indiana]
  • A. transportationNearby
    Indicates that there is a transportation facility or service located close to the referenced entity.
  • B. hasTransportationProximityTo
    Indicates that one entity is located near or conveniently accessible to another entity in terms of transportation options or routes.
  • C. transportationRole
    Indicates a role or function that an entity has specifically in the context of providing, operating, or supporting transportation.
  • D. operatorOfNearbyTransit
    Indicates that an entity operates or manages a public transit service located in close geographic proximity to another specified entity.
  • E. hasNearbyTransportationCorridor chosen
    Indicates that an entity is located close to a significant transportation route or corridor, such as a road, railway, or transit line.
  • 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_69f349dabc008190a18999c26682ed47 completed April 30, 2026, 12:23 p.m.
NER Named-entity recognition batch_69ff2d22ffb48190ae58ddf3c7e02869 completed May 9, 2026, 12:48 p.m.
PD Predicate disambiguation batch_69ff2ac2e1c4819096cc64e94aef2ff0 completed May 9, 2026, 12:38 p.m.
Created at: May 1, 2026, 2:05 a.m.