Triple
T34177264
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UAAA |
E876706
|
entity |
| Predicate | supportsInstrumentApproach |
P24736
|
FINISHED |
| Object | ILS |
E206887
|
NE 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: ILS | Statement: [UAAA, supportsInstrumentApproach, ILS]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsInstrumentApproach Context triple: [UAAA, supportsInstrumentApproach, ILS]
-
A.
supportsInstrumentApproaches
chosen
Indicates that one entity provides the capability, infrastructure, or authorization for instrument-based approach procedures to be conducted by another entity.
-
B.
hasInstrumentApproach
Indicates that an approach procedure to a location or runway is conducted using specified navigation instruments or instrument-based methods.
-
C.
supportsInstrument
Indicates that one entity provides assistance, resources, or functionality that enables another entity (the instrument) to operate or be used effectively.
-
D.
supportsControlApproach
Indicates that one entity provides the basis, justification, or compatibility for using a particular control approach associated with another entity.
-
E.
supportedInstrumentRating
Indicates that one entity has provided assistance, endorsement, or resources enabling another entity to obtain or maintain an instrument rating.
- F. None of above.
Provenance (4 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_69f349ad97ac8190bf1f17417c970e64 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a36c1de65648190a5ac61543c335e87 |
completed | June 20, 2026, 4:37 p.m. |
| PD | Predicate disambiguation | batch_6a0379f963908190846d232f386fd98f |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:54 a.m.