Triple
T18579124
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | KOXV |
E454061
|
entity |
| Predicate | runway13TrueHeading |
P70220
|
FINISHED |
| Object | approximately 130 degrees |
—
|
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: approximately 130 degrees | Statement: [KOXV, runway13TrueHeading, approximately 130 degrees]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: runway13TrueHeading Context triple: [KOXV, runway13TrueHeading, approximately 130 degrees]
-
A.
runwayEndHeading
chosen
Indicates the directional heading or bearing associated with the end of a runway, typically expressed in degrees relative to north.
-
B.
runway
Indicates a relationship where a runway serves as the takeoff and landing surface used by aircraft at an airport or airfield.
-
C.
isPrimaryRunwayOf
Indicates that a runway serves as the main or principal runway for a particular airport or airfield.
-
D.
isRunwayOf
Indicates that a physical runway is a component or facility belonging to, used by, or officially associated with a particular airport or airfield.
-
E.
runwayPresence
Indicates the existence or availability of a runway at or associated with the referenced location or facility.
- 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_69d8d38974308190a9174430ef256b73 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e543ce63188190b14a37c5ca9c2726 |
completed | April 19, 2026, 9:06 p.m. |
| PD | Predicate disambiguation | batch_69e478c98d4c81909d37a0e72c6e7bd0 |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:43 a.m.