Triple
T20945520
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bergstrom Air Force Base |
E515832
|
entity |
| Predicate | hadRunway |
P51630
|
FINISHED |
| Object | runway 12R/30L |
—
|
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: runway 12R/30L | Statement: [Bergstrom Air Force Base, hadRunway, runway 12R/30L]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadRunway Context triple: [Bergstrom Air Force Base, hadRunway, runway 12R/30L]
-
A.
usesRunwayOf
Indicates that one entity makes use of the runway that belongs to or is associated with another entity.
-
B.
hasWalkedRunwayFor
Indicates that one entity has modeled or appeared on the fashion runway in a show organized by another entity.
-
C.
hasRunwaySide
Indicates that a runway is located on or associated with a particular side or boundary of another feature (such as an airport or airfield area).
-
D.
hasRunwayNumber
Indicates that an airport or airfield runway is assigned a specific identifying number.
-
E.
hasRunwayPresence
chosen
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_69e0b4fcd678819087a304291f14330a |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6fad7f67481908675e76736f5e0c3 |
completed | April 21, 2026, 4:19 a.m. |
| PD | Predicate disambiguation | batch_69e5c9b1bae48190a845165fed1b005e |
completed | April 20, 2026, 6:37 a.m. |
Created at: April 16, 2026, 12:56 p.m.