Triple
T19717522
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UGTB |
E473517
|
entity |
| Predicate | runway13_31Usage |
P137054
|
FINISHED |
| Object | instrument flight operations |
—
|
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: instrument flight operations | Statement: [UGTB, runway13_31Usage, instrument flight operations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: runway13_31Usage Context triple: [UGTB, runway13_31Usage, instrument flight operations]
-
A.
runway12_30Usage
Indicates the use or operational status of runway 12/30 for aircraft movements or related airport activities.
-
B.
runway03_21Use
Indicates use or operational status of runway 03/21 for aircraft movements or related airport activities.
-
C.
runway11_29Use
Indicates that runway 11/29 is being used for aircraft operations such as takeoffs or landings.
-
D.
runway17_35Use
Indicates use or operational activity occurring on runway 17/35.
-
E.
runway
Indicates a relationship where a runway serves as the takeoff and landing surface used by aircraft at an airport or airfield.
- F. None of above. chosen
Provenance (4 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_69d8e516dd048190a0b6c93ea3e71f58 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e6440ec9e881909b75c0ebefab827f |
completed | April 20, 2026, 3:19 p.m. |
| PD | Predicate disambiguation | batch_69e530438c60819082364c7be3eef6f0 |
completed | April 19, 2026, 7:42 p.m. |
| PDg | Predicate description generation | batch_69e532bbedf081908d801600e2af94a7 |
completed | April 19, 2026, 7:53 p.m. |
Created at: April 10, 2026, 1:46 p.m.