Triple
T16710971
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | KIKR |
E406104
|
entity |
| Predicate | hasApproachProcedures |
P8864
|
FINISHED |
| Object | instrument approach procedures |
—
|
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 approach procedures | Statement: [KIKR, hasApproachProcedures, instrument approach procedures]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasApproachProcedures Context triple: [KIKR, hasApproachProcedures, instrument approach procedures]
-
A.
hasVisualApproachProcedures
Indicates that an entity has associated visual approach procedures defined or available for use.
-
B.
hasComplexArrivalProcedures
Indicates that the arrival process for an entity involves multiple steps, conditions, or special requirements beyond a simple or standard arrival.
-
C.
hasInstrumentApproach
chosen
Indicates that an approach procedure to a location or runway is conducted using specified navigation instruments or instrument-based methods.
-
D.
hasRunwayApproachType
Indicates the specific type or category of approach procedure associated with a runway.
-
E.
hasComplexDepartureProcedures
Indicates that the departure process from a location or system involves multiple steps, conditions, or special rules beyond a simple or standard departure.
- 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_69d8838db21081909589220fd71440a4 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e386523fc08190a13a4232af191992 |
completed | April 18, 2026, 1:25 p.m. |
| PD | Predicate disambiguation | batch_69e319c379f88190ac0adf812486f598 |
completed | April 18, 2026, 5:42 a.m. |
Created at: April 10, 2026, 5:20 a.m.