Triple
T36914704
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EGPD |
E913012
|
entity |
| Predicate | associatedAirportHasInstrumentApproach |
P24736
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [EGPD, associatedAirportHasInstrumentApproach, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedAirportHasInstrumentApproach Context triple: [EGPD, associatedAirportHasInstrumentApproach, true]
-
A.
hasInstrumentApproach
Indicates that an approach procedure to a location or runway is conducted using specified navigation instruments or instrument-based methods.
-
B.
hasRunwayApproachType
Indicates the specific type or category of approach procedure associated with a runway.
-
C.
hasVisualApproachProcedures
Indicates that an entity has associated visual approach procedures defined or available for use.
-
D.
isOnlyInstrumentAirportOn
Indicates that the referenced airport is the only one at that location equipped and authorized for instrument flight operations.
-
E.
supportsInstrumentApproaches
chosen
Indicates that one entity provides the capability, infrastructure, or authorization for instrument-based approach procedures to be conducted by another entity.
- 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_69f76e879768819085c2fb31a6a5b44b |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037c8e2c648190a65fc9c7872861af |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a10036481909c71188b2a0e7f04 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:13 p.m.