Triple

T30363305
Position Surface form Disambiguated ID Type / Status
Subject Fairfield, Iowa E772348 entity
Predicate hasNearbyAirport P4363 FINISHED
Object Fairfield Municipal Airport
Fairfield Municipal Airport is a public-use airport serving the city of Fairfield and the surrounding region in Jefferson County, Iowa.
E1912036 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: Fairfield Municipal Airport | Statement: [Fairfield, Iowa, hasNearbyAirport, Fairfield Municipal Airport]
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Fairfield Municipal Airport
Triple: [Fairfield, Iowa, hasNearbyAirport, Fairfield Municipal Airport]
Generated description
Fairfield Municipal Airport is a public-use airport serving the city of Fairfield and the surrounding region in Jefferson County, Iowa.

Provenance (5 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_69f2248d71408190aec0d5c2001b1cff completed April 29, 2026, 3:32 p.m.
NER Named-entity recognition batch_69f6827e194481908018f91cbff12bc2 completed May 2, 2026, 11:02 p.m.
NED1 Entity disambiguation (via context triple) batch_6a27893994548190958b3949339a6bd6 completed June 9, 2026, 3:32 a.m.
NEDg Description generation batch_6a2789b0aa20819083c98812c930d2f7 completed June 9, 2026, 3:34 a.m.
NED2 Entity disambiguation (via description) batch_6a278a634fdc819087ca98974c07aa55 completed June 9, 2026, 3:37 a.m.
Created at: April 29, 2026, 7:58 p.m.