Triple
T11955918
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EFKA |
E284552
|
entity |
| Predicate | hasRunway |
P105
|
FINISHED |
| Object | Runway 17/35 |
E380073
|
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 17/35 | Statement: [EFKA, hasRunway, Runway 17/35]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Runway 17/35 Context triple: [EFKA, hasRunway, Runway 17/35]
-
A.
Runway 17/35
chosen
Runway 17/35 is a primary paved runway used for aircraft operations at Kauhava Air Base in Finland.
-
B.
Runway 17/35
Runway 17/35 is a primary paved runway at Essendon Airport in Melbourne, Australia, used for a mix of general aviation, corporate, and regional aircraft operations.
-
C.
Runway 17/35
Runway 17/35 is one of the primary paved runways at Minneapolis–Saint Paul International Airport, used for both commercial and general aviation operations.
-
D.
Runway 17/35
Runway 17/35 is a primary paved runway at Wilmington International Airport in North Carolina, used for both commercial and general aviation operations.
-
E.
Runway 17/35
Runway 17/35 is a primary paved runway at Pensacola Naval Air Station used for military aircraft operations.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (3 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_69d6ab2db38c8190b1f0ed6663ef8ada |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d90366fda8819083168c93abad27d4 |
completed | April 10, 2026, 2:04 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f65e94b6008190ae19c245c4c62b5e |
completed | May 2, 2026, 8:29 p.m. |
Created at: April 8, 2026, 9:45 p.m.