Triple

T1067086
Position Surface form Disambiguated ID Type / Status
Subject U.S. Route 29 E23234 entity
Predicate connectsCity P4245 FINISHED
Object Opelika, Alabama E132736 NE 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: Opelika, Alabama | Statement: [U.S. Route 29, connectsCity, Opelika, Alabama]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Opelika, Alabama
Context triple: [U.S. Route 29, connectsCity, Opelika, Alabama]
  • A. Opelika chosen
    Opelika is a city in eastern Alabama known for its proximity to Auburn and its role as a regional center for industry and commerce.
  • B. Saraland
    Saraland is a suburban city in Mobile County, Alabama, known as part of the Mobile metropolitan area and for its residential communities and local industry.
  • C. Fayetteville, Alabama
    Fayetteville, Alabama is an unincorporated rural community located in Shelby County in the central part of the state.
  • D. Kingston, Alabama
    Kingston, Alabama is an unincorporated rural community located in Shelby County in the central part of the state.
  • E. Fairfield, Alabama
    Fairfield, Alabama is a small city in Jefferson County that functions as a residential and industrial suburb of Birmingham within central Alabama.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69a493ee1f908190992b5f0d1b04459b completed March 1, 2026, 7:30 p.m.
NER Named-entity recognition batch_69a4b911f06881908659cb85ba1e05e0 completed March 1, 2026, 10:09 p.m.
NED1 Entity disambiguation (via context triple) batch_69ad519194988190bb0eb59e7fa34dea completed March 8, 2026, 10:38 a.m.
Created at: March 1, 2026, 7:42 p.m.