Triple
T38020894
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Runway 13/31 |
E948625
|
entity |
| Predicate | isMainTrainingRunwayAt |
P8867
|
FINISHED |
| Object | W. K. Kellogg Airport |
—
|
NE NERFINISHED |
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: W. K. Kellogg Airport | Statement: [Runway 13/31, isMainTrainingRunwayAt, W. K. Kellogg Airport]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isMainTrainingRunwayAt Context triple: [Runway 13/31, isMainTrainingRunwayAt, W. K. Kellogg Airport]
-
A.
isPrimaryRunwayOf
chosen
Indicates that a runway serves as the main or principal runway for a particular airport or airfield.
-
B.
isRunwayOf
Indicates that a physical runway is a component or facility belonging to, used by, or officially associated with a particular airport or airfield.
-
C.
isCentralRunway
Indicates that a given runway serves as the primary or central runway within an airport or airfield layout.
-
D.
isInstrumentRunway
Indicates that a runway is designated and equipped for instrument-based approaches and departures rather than solely visual operations.
-
E.
hasRunwayPresence
Indicates that an entity maintains a physical runway or landing strip suitable for aircraft operations.
- 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_69f76efc10448190aff5fb566b98f952 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fbc995dc2481908b3bd4217f8101e7 |
completed | May 6, 2026, 11:07 p.m. |
| PD | Predicate disambiguation | batch_69fbc8ee04f08190977b7ad70fc85896 |
completed | May 6, 2026, 11:04 p.m. |
Created at: May 3, 2026, 4:20 p.m.