Triple

T20728493
Position Surface form Disambiguated ID Type / Status
Subject Bert Mooney Airport E509502 entity
Predicate locatedIn P40 FINISHED
Object Butte 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: Butte | Statement: [Bert Mooney Airport, locatedIn, Butte]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Butte
Context triple: [Bert Mooney Airport, locatedIn, Butte]
  • A. Butte
    Butte is a small census-designated community in the Matanuska-Susitna Borough of Alaska, known for its rural character and proximity to Palmer and the Matanuska River.
  • B. Butte City
    Butte City is a small rural community located in Glenn County in the northern part of California.
  • C. Butte, Montana chosen
    Butte, Montana is a historic mining city in southwestern Montana known for its rich copper-mining heritage and well-preserved Old West character.
  • D. Missoula
    Missoula is a vibrant city in western Montana known for its university, outdoor recreation, and cultural scene.
  • E. Butte City, Idaho
    Butte City, Idaho is a small rural town in eastern Idaho known for its historic ties to regional mining and agriculture.
  • 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_69e0b4c4cc648190b45fda6e2b20af56 completed April 16, 2026, 10:07 a.m.
NER Named-entity recognition batch_69e6c1e9ed708190ad8e371646630fea completed April 21, 2026, 12:16 a.m.
Created at: April 16, 2026, 12:30 p.m.