Triple
T2774850
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eppley Airfield |
E61543
|
entity |
| Predicate | hasRunway |
P105
|
FINISHED |
| Object |
Runway 14R/32L
Runway 14R/32L is a primary paved runway used for aircraft takeoffs and landings at Eppley Airfield in Omaha, Nebraska.
|
E407584
|
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 14R/32L | Statement: [Eppley Airfield, hasRunway, Runway 14R/32L]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Runway 14R/32L Context triple: [Eppley Airfield, hasRunway, Runway 14R/32L]
-
A.
Runway 14R/32L
Runway 14R/32L is a primary paved runway at Moffett Field in California, used for military, research, and general aviation operations.
-
B.
Runway 14R/32L
Runway 14R/32L is a primary paved runway used for aircraft takeoffs and landings at Osaka International Airport in Japan.
-
C.
Runway 14R/32L
Runway 14R/32L is a primary paved runway at Moscow’s Domodedovo International Airport used for handling commercial air traffic.
-
D.
Runway 14L/32R
Runway 14L/32R is one of the primary paved runways at Moffett Field in California, used for military, research, and general aviation operations.
-
E.
Runway 16L/34R
Runway 16L/34R is a primary paved runway at Reno–Tahoe International Airport used for commercial and general aviation takeoffs and landings.
- 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 14R/32L Triple: [Eppley Airfield, hasRunway, Runway 14R/32L]
Generated description
Runway 14R/32L is a primary paved runway used for aircraft takeoffs and landings at Eppley Airfield in Omaha, Nebraska.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Runway 14R/32L Target entity description: Runway 14R/32L is a primary paved runway used for aircraft takeoffs and landings at Eppley Airfield in Omaha, Nebraska.
-
A.
Runway 14R/32L
Runway 14R/32L is a primary paved runway at Moscow’s Domodedovo International Airport used for handling commercial air traffic.
-
B.
Runway 14R/32L
Runway 14R/32L is a primary paved runway at Moffett Field in California, used for military, research, and general aviation operations.
-
C.
Runway 14R/32L
Runway 14R/32L is a primary paved runway used for aircraft takeoffs and landings at Osaka International Airport in Japan.
-
D.
Runway 14L/32R
Runway 14L/32R is one of the primary paved runways at Moffett Field in California, used for military, research, and general aviation operations.
-
E.
Runway 16L/34R
Runway 16L/34R is a primary paved runway at Reno–Tahoe International Airport used for commercial and general aviation takeoffs and landings.
- 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_69ab4b7cd13481909174bca9809ed259 |
completed | March 6, 2026, 9:47 p.m. |
| NER | Named-entity recognition | batch_69abdd7f9570819087f1b1cb59d68586 |
completed | March 7, 2026, 8:10 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b54c16c05481908f451b492ca9f47f |
completed | March 14, 2026, 11:52 a.m. |
| NEDg | Description generation | batch_69b54fd243888190aba6b39d20608f69 |
completed | March 14, 2026, 12:08 p.m. |
| NED2 | Entity disambiguation (via description) | batch_69b5502f28808190af903cfc81f99d61 |
completed | March 14, 2026, 12:10 p.m. |
Created at: March 6, 2026, 9:57 p.m.