Triple
T3356731
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zurich Airport |
E70621
|
entity |
| Predicate | supportsInstrumentLandingSystem |
P24736
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Zurich Airport, supportsInstrumentLandingSystem, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsInstrumentLandingSystem Context triple: [Zurich Airport, supportsInstrumentLandingSystem, yes]
-
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.
plannedLandingMethod
Indicates that an entity has designated a specific method or procedure to be used for its landing.
-
E.
supportsLaunchVehicle
Indicates that one entity provides the necessary structural, mechanical, or operational backing for the successful deployment or functioning of a launch vehicle.
- 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_69ad85a660c48190998489309a3b4869 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb242d4988190bbac993df587936d |
completed | March 8, 2026, 5:30 p.m. |
| PD | Predicate disambiguation | batch_69ada42fbe7c8190b9f185b5ab985f17 |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:13 p.m.