Triple
T24159690
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Emporia Municipal Airport |
E598796
|
entity |
| Predicate | runway 1 designation |
P123236
|
FINISHED |
| Object | 1/19 |
—
|
LITERAL 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: 1/19 | Statement: [Emporia Municipal Airport, runway 1 designation, 1/19]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: runway 1 designation Context triple: [Emporia Municipal Airport, runway 1 designation, 1/19]
-
A.
hasRunwayDesignationSide
Indicates that a runway designation is associated with a specific side or direction of the runway (e.g., left, right, or center).
-
B.
hasRunwayDesignatorType
Indicates the specific type or classification of a runway’s designator used to identify that runway.
-
C.
runwayName
chosen
Indicates the designated name or identifier assigned to a runway.
-
D.
runway
Indicates a relationship where a runway serves as the takeoff and landing surface used by aircraft at an airport or airfield.
-
E.
usesRunwayNumberingConvention
Indicates that an airport or runway follows a specific standardized system for assigning runway identification numbers.
- F. None of above.
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_69e288cb0a3081909ef221744f274384 |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1e0e7f8e481909c55ae66bf7b16e9 |
completed | April 29, 2026, 10:43 a.m. |
| PD | Predicate disambiguation | batch_69f176585f3481909beb907de252cd98 |
completed | April 29, 2026, 3:09 a.m. |
Created at: April 17, 2026, 11:32 p.m.