Triple
T8393380
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grand Forks International Airport |
E197995
|
entity |
| Predicate | hasRunway |
P105
|
FINISHED |
| Object |
Runway 9L/27R
Runway 9L/27R is a primary paved runway at Grand Forks International Airport used for aircraft takeoffs and landings.
|
E765492
|
NE FINISHED |
How this triple was built (4 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 9L/27R | Statement: [Grand Forks International Airport, hasRunway, Runway 9L/27R]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Runway 9L/27R Context triple: [Grand Forks International Airport, hasRunway, Runway 9L/27R]
-
A.
Runway 9L/27R
Runway 9L/27R is a primary paved runway used for aircraft takeoffs and landings at Orlando Sanford International Airport in Florida.
-
B.
Runway 9L/27R
Runway 9L/27R is a primary paved runway used for aircraft takeoffs and landings at Melbourne Orlando International Airport in Florida.
-
C.
Runway 9R/27L
Runway 9R/27L is a primary paved runway at Orlando Sanford International Airport used for commercial and general aviation operations.
-
D.
Runway 9/27
Runway 9/27 is a primary east–west runway at Memphis International Airport used for commercial and cargo aircraft operations.
-
E.
Runway 9/27
Runway 9/27 is a primary east–west runway at Tallahassee International Airport used for commercial and general aviation operations.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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 9L/27R Triple: [Grand Forks International Airport, hasRunway, Runway 9L/27R]
Generated description
Runway 9L/27R is a primary paved runway at Grand Forks International Airport used for aircraft takeoffs and landings.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Runway 9L/27R Target entity description: Runway 9L/27R is a primary paved runway at Grand Forks International Airport used for aircraft takeoffs and landings.
-
A.
Runway 9L/27R
Runway 9L/27R is a primary paved runway used for aircraft takeoffs and landings at Orlando Sanford International Airport in Florida.
-
B.
Runway 9L/27R
Runway 9L/27R is a primary paved runway used for aircraft takeoffs and landings at Melbourne Orlando International Airport in Florida.
-
C.
Runway 9R/27L
Runway 9R/27L is a primary paved runway at Orlando Sanford International Airport used for commercial and general aviation operations.
-
D.
Runway 9/27
Runway 9/27 is a primary east–west runway at Memphis International Airport used for commercial and cargo aircraft operations.
-
E.
Runway 9/27
Runway 9/27 is a primary east–west runway at Tallahassee International Airport used for commercial and general aviation operations.
- F. None of above. chosen
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_69ca82f816bc8190ab321c07d72208c1 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb8184788081909e9857afff629985 |
completed | March 31, 2026, 8:10 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cfb9f030fc8190961bcb067350e3e6 |
completed | April 3, 2026, 1 p.m. |
| NEDg | Description generation | batch_69cfbacea9408190a38f14817437c382 |
completed | April 3, 2026, 1:04 p.m. |
| NED2 | Entity disambiguation (via description) | batch_69cfbb6235148190850865a734d55a6c |
completed | April 3, 2026, 1:06 p.m. |
Created at: March 30, 2026, 6:03 p.m.