Triple

T30333347
Position Surface form Disambiguated ID Type / Status
Subject Valdosta Regional Airport E771546 entity
Predicate runway P1654 FINISHED
Object Runway 4/22
Runway 4/22 is one of the primary paved runways at Valdosta Regional Airport in Georgia, used for general aviation and commercial flight operations.
E2072485 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: Runway 4/22 | Statement: [Valdosta Regional Airport, runway, Runway 4/22]
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: Runway 4/22
Triple: [Valdosta Regional Airport, runway, Runway 4/22]
Generated description
Runway 4/22 is one of the primary paved runways at Valdosta Regional Airport in Georgia, used for general aviation and commercial flight operations.

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_69f2248aba24819095bb86480d55b23b completed April 29, 2026, 3:32 p.m.
NER Named-entity recognition batch_69f681cad3f08190bf4224b74ea5852c completed May 2, 2026, 10:59 p.m.
NED1 Entity disambiguation (via context triple) batch_6a36821810088190a3f3d84b4551e147 completed June 20, 2026, 12:05 p.m.
NEDg Description generation batch_6a3682a474508190a277eab3840b9034 completed June 20, 2026, 12:08 p.m.
NED2 Entity disambiguation (via description) batch_6a36830e85b081909df2487f5f48caf9 completed June 20, 2026, 12:09 p.m.
Created at: April 29, 2026, 7:53 p.m.