Triple

T28948761
Position Surface form Disambiguated ID Type / Status
Subject Grand Forks International Airport E730949 entity
Predicate hasRunway P105 FINISHED
Object Runway 17L/35R
Runway 17L/35R is one of the primary paved runways at Grand Forks International Airport, used for both commercial and general aviation operations.
E752633 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 17L/35R | Statement: [Grand Forks International Airport, hasRunway, Runway 17L/35R]
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 17L/35R
Triple: [Grand Forks International Airport, hasRunway, Runway 17L/35R]
Generated description
Runway 17L/35R is one of the primary paved runways at Grand Forks International Airport, used for both commercial and general aviation 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_69f043eb9bcc819091ac7b07aecb6475 completed April 28, 2026, 5:21 a.m.
NER Named-entity recognition batch_69f65b8a9a6c819091b9ec4563704490 completed May 2, 2026, 8:16 p.m.
NED1 Entity disambiguation (via context triple) batch_6a33e87559e88190b8ef201f892189c1 completed June 18, 2026, 12:45 p.m.
NEDg Description generation batch_6a33e954d89881908ea05c9e466780fa completed June 18, 2026, 12:49 p.m.
NED2 Entity disambiguation (via description) batch_6a342c695e348190957d2cf24a4bc080 completed June 18, 2026, 5:35 p.m.
Created at: April 28, 2026, 8:42 a.m.