Triple
T32951641
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Runway 9L/27R |
E842971
|
entity |
| Predicate | supportsVisualApproach |
—
|
GENERATED |
| Object | true |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsVisualApproach Context triple: [Runway 9L/27R, supportsVisualApproach, true]
-
A.
visualApproach
Indicates that one entity moves toward or aligns with another primarily using visual cues or sight-based guidance.
-
B.
supportsInstrumentApproaches
Indicates that one entity provides the capability, infrastructure, or authorization for instrument-based approach procedures to be conducted by another entity.
-
C.
hasVisualApproachProcedures
chosen
Indicates that an entity has associated visual approach procedures defined or available for use.
-
D.
hasInstrumentApproach
Indicates that an approach procedure to a location or runway is conducted using specified navigation instruments or instrument-based methods.
-
E.
supportsControlApproach
Indicates that one entity provides the basis, justification, or compatibility for using a particular control approach associated with another entity.
- F. None of above.
Provenance (1 batch)
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_69f3494a31f481909057136e49b4fe60 |
completed | April 30, 2026, 12:21 p.m. |
Created at: May 1, 2026, 1:21 a.m.