Triple

T18143670
Position Surface form Disambiguated ID Type / Status
Subject Auburn University Regional Airport E434325 entity
Predicate locatedIn P40 FINISHED
Object Auburn, Alabama 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: Auburn, Alabama | Statement: [Auburn University Regional Airport, locatedIn, Auburn, Alabama]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Auburn, Alabama
Context triple: [Auburn University Regional Airport, locatedIn, Auburn, Alabama]
  • A. Auburn, Georgia
    Auburn, Georgia is a small city in Barrow and Gwinnett counties within the Atlanta metropolitan area.
  • B. Auburn chosen
    Auburn is a city in eastern Alabama known for being home to Auburn University and its strong college-town atmosphere.
  • C. Auburn
    Auburn is a small city in northeastern Indiana known for its automotive heritage and classic car museums.
  • D. Auburn
    Auburn is a residential neighborhood located within the city of Cranston, Rhode Island.
  • E. Auburn
    Auburn is a historic Gold Rush-era city in California’s Sierra Nevada foothills, known for its preserved Old Town and role in the state’s mining heritage.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69d8b90aac308190801e2c57d8c5bfe5 completed April 10, 2026, 8:47 a.m.
NER Named-entity recognition batch_69e4de0da3e081908732ed022f5eb90a completed April 19, 2026, 1:52 p.m.
Created at: April 10, 2026, 10:29 a.m.