Triple
T23904762
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | KSMO |
E601158
|
entity |
| Predicate | hasApproachProcedure |
P19670
|
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: [KSMO, hasApproachProcedure, instrument approach procedures]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasApproachProcedure Context triple: [KSMO, hasApproachProcedure, instrument approach procedures]
-
A.
hasInstrumentApproach
Indicates that an approach procedure to a location or runway is conducted using specified navigation instruments or instrument-based methods.
-
B.
hasApproachControl
Indicates that one entity exercises approach control authority or responsibility over another entity, typically managing its approach phase or access.
-
C.
hasRunwayApproachType
chosen
Indicates the specific type or category of approach procedure associated with a runway.
-
D.
hasVisualApproachProcedures
Indicates that an entity has associated visual approach procedures defined or available for use.
-
E.
hasApproachTrail
Indicates that there is a designated trail or path providing access or approach to a particular location or feature.
- 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_69e295364a488190bcac702e9bb7f764 |
completed | April 17, 2026, 8:16 p.m. |
| NER | Named-entity recognition | batch_69f1cde13e88819086bbd0bc4a5b6a36 |
completed | April 29, 2026, 9:22 a.m. |
| PD | Predicate disambiguation | batch_69f1614e24b48190a1c8fb5b7c75ee0f |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 8:26 p.m.