Triple
T10438810
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | KBOS runway system |
E246112
|
entity |
| Predicate | supportsApproachType |
P24736
|
FINISHED |
| Object | instrument approaches |
—
|
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 approaches | Statement: [KBOS runway system, supportsApproachType, instrument approaches]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsApproachType Context triple: [KBOS runway system, supportsApproachType, instrument approaches]
-
A.
hasApproachType
Indicates the specific method, strategy, or manner in which an action, process, or interaction is carried out or approached.
-
B.
supportsControlApproach
Indicates that one entity provides the basis, justification, or compatibility for using a particular control approach associated with another entity.
-
C.
includesApproach
Indicates that one entity incorporates, utilizes, or is characterized by a particular method, strategy, or approach in relation to another entity or context.
-
D.
supportsInstrumentApproaches
chosen
Indicates that one entity provides the capability, infrastructure, or authorization for instrument-based approach procedures to be conducted by another entity.
-
E.
supportsType
Indicates that one entity is capable of handling, accepting, or being compatible with a specified type.
- 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_69d381bf3dc08190bf35a2643e4e8f22 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4fe083cd881909d2d8ad75d1d94cb |
completed | April 7, 2026, 12:52 p.m. |
| PD | Predicate disambiguation | batch_69d4fb73a5e48190a8df4775bc5da80f |
completed | April 7, 2026, 12:41 p.m. |
Created at: April 6, 2026, 12:14 p.m.