Triple
T10690165
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Virgil I. Grissom Municipal Airport |
E251988
|
entity |
| Predicate | runwayOrientation_12_30 |
P6272
|
FINISHED |
| Object | 120/300 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: 120/300 degrees | Statement: [Virgil I. Grissom Municipal Airport, runwayOrientation_12_30, 120/300 degrees]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: runwayOrientation_12_30 Context triple: [Virgil I. Grissom Municipal Airport, runwayOrientation_12_30, 120/300 degrees]
-
A.
runway12_30Usage
Indicates the use or operational status of runway 12/30 for aircraft movements or related airport activities.
-
B.
runwayEndHeading
Indicates the directional heading or bearing associated with the end of a runway, typically expressed in degrees relative to north.
-
C.
hasRunwayOrientation
chosen
Indicates that a runway is aligned or oriented in a specific directional heading.
-
D.
hasRightRunwayIn25Direction
Indicates that an entity (typically an airport or airfield) possesses a right-hand runway aligned or oriented in the 25 direction.
-
E.
runwayEnd
Indicates that one entity represents the end point or terminus of a runway associated with the other entity.
- 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_69d6aa5bd7c08190a816e733b4045c23 |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d6fd1c0f0081908a6869ee756ec789 |
completed | April 9, 2026, 1:13 a.m. |
| PD | Predicate disambiguation | batch_69d6dd8cc0788190b4c02a772e4b58b3 |
completed | April 8, 2026, 10:58 p.m. |
Created at: April 8, 2026, 9:11 p.m.