Triple
T20569160
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Topeka Regional Airport |
E505043
|
entity |
| Predicate | hasSecondaryRunwayDesignation |
P130266
|
FINISHED |
| Object | 3/21 |
—
|
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: 3/21 | Statement: [Topeka Regional Airport, hasSecondaryRunwayDesignation, 3/21]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSecondaryRunwayDesignation Context triple: [Topeka Regional Airport, hasSecondaryRunwayDesignation, 3/21]
-
A.
hasSecondaryRunway
chosen
Indicates that an entity possesses an additional runway beyond its primary runway.
-
B.
hasParallelRunwayIndicator
Indicates that one runway serves as a parallel counterpart or reference indicator for another runway within an airport or airfield.
-
C.
hasRunwayDesignationSide
Indicates that a runway designation is associated with a specific side or direction of the runway (e.g., left, right, or center).
-
D.
hasParallelRunway
Indicates that one runway is parallel in orientation and alignment to another runway.
-
E.
isPrimaryRunwayOf
Indicates that a runway serves as the main or principal runway for a particular airport or airfield.
- 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_69e0b4b721588190993ac7b0a9be2736 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6a7a4b90c81909854dac72f671eec |
completed | April 20, 2026, 10:24 p.m. |
| PD | Predicate disambiguation | batch_69e59ff0116c8190a163ff28ed01430a |
completed | April 20, 2026, 3:39 a.m. |
Created at: April 16, 2026, 11:39 a.m.