Triple

T26852740
Position Surface form Disambiguated ID Type / Status
Subject Avon Park, Florida E676101 entity
Predicate hasAirportNearby P4363 FINISHED
Object Avon Park Executive Airport
Avon Park Executive Airport is a public-use airport serving general aviation needs for the city of Avon Park in central Florida.
E1750807 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: Avon Park Executive Airport | Statement: [Avon Park, Florida, hasAirportNearby, Avon Park Executive 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: Avon Park Executive Airport
Triple: [Avon Park, Florida, hasAirportNearby, Avon Park Executive Airport]
Generated description
Avon Park Executive Airport is a public-use airport serving general aviation needs for the city of Avon Park in central Florida.

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_69eee9b9d7708190a15d7485709ae981 completed April 27, 2026, 4:44 a.m.
NER Named-entity recognition batch_69f61b93f6d88190beffbcd2e9374a61 completed May 2, 2026, 3:43 p.m.
NED1 Entity disambiguation (via context triple) batch_6a12298815e08190b333b7d1324754d1 completed May 23, 2026, 10:26 p.m.
NEDg Description generation batch_6a122b0175188190be2cb1b106694112 completed May 23, 2026, 10:32 p.m.
NED2 Entity disambiguation (via description) batch_6a122b8f21ec81908aaaf7e829c62f85 completed May 23, 2026, 10:34 p.m.
Created at: April 27, 2026, 5:18 a.m.