Triple
T21470391
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Central Nebraska Regional Airport |
E529713
|
entity |
| Predicate | runway13/31Orientation |
P6272
|
FINISHED |
| Object | 13/31 |
—
|
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: 13/31 | Statement: [Central Nebraska Regional Airport, runway13/31Orientation, 13/31]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: runway13/31Orientation Context triple: [Central Nebraska Regional Airport, runway13/31Orientation, 13/31]
-
A.
hasRunwayOrientation
chosen
Indicates that a runway is aligned or oriented in a specific directional heading.
-
B.
runway13_31Usage
Indicates how runway 13/31 is used, such as the type, frequency, or conditions of its operational usage.
-
C.
runway
Indicates a relationship where a runway serves as the takeoff and landing surface used by aircraft at an airport or airfield.
-
D.
runway03_21Use
Indicates use or operational status of runway 03/21 for aircraft movements or related airport activities.
-
E.
trailOrientation
Indicates the directional alignment or facing direction of a trail relative to a reference frame or compass directions.
- 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_69e0c459acb481909bb6ee452a0045c7 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69e9ea12d9048190bf51ca3efc435a64 |
completed | April 23, 2026, 9:44 a.m. |
| PD | Predicate disambiguation | batch_69e631ec1d048190b6da97da8222e413 |
completed | April 20, 2026, 2:02 p.m. |
Created at: April 16, 2026, 6:17 p.m.