Triple

T18217714
Position Surface form Disambiguated ID Type / Status
Subject Goshen Municipal Airport E436206 entity
Predicate operator P179 FINISHED
Object City of Goshen 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: City of Goshen | Statement: [Goshen Municipal Airport, operator, City of Goshen]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: City of Goshen
Context triple: [Goshen Municipal Airport, operator, City of Goshen]
  • A. Goshen
    Goshen was a short-lived Boer republic in southern Africa established by Voortrekker settlers during the 1880s.
  • B. Goshen chosen
    Goshen is a small city in northern Indiana known for its manufacturing base, Mennonite and Amish heritage, and historic downtown.
  • C. Goshen
    Goshen is a small town in Utah County, Utah, situated in the southern part of Utah Valley.
  • D. Goshen
    Goshen is the fertile region in ancient Egypt where the Israelites settled during the time of Joseph, as recounted in the Book of Genesis.
  • E. Usshertown
    Usshertown is a historic coastal neighborhood within Accra’s old Ga Mashie district, known for its Ga heritage and colonial-era architecture.
  • 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_69d8b9103a8081908bbb0836fef10efd completed April 10, 2026, 8:47 a.m.
NER Named-entity recognition batch_69e4e4782db4819093baee57f34be490 completed April 19, 2026, 2:19 p.m.
Created at: April 10, 2026, 10:32 a.m.