Triple
T4331728
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Corfu International Airport |
E96764
|
entity |
| Predicate | usesRunwayApproach |
P14085
|
FINISHED |
| Object | approach over water |
—
|
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: approach over water | Statement: [Corfu International Airport, usesRunwayApproach, approach over water]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesRunwayApproach Context triple: [Corfu International Airport, usesRunwayApproach, approach over water]
-
A.
usesRunwayOf
Indicates that one entity makes use of the runway that belongs to or is associated with another entity.
-
B.
hasRunwayApproachType
Indicates the specific type or category of approach procedure associated with a runway.
-
C.
runwayApproachOver
chosen
Indicates that an aircraft’s approach path to a runway passes over a particular object, area, or feature.
-
D.
hasRunwayAccessTo
Indicates that one location or facility is directly connected to another via a usable runway, allowing aircraft to move between them without leaving runway infrastructure.
-
E.
hasRunwayAccessVia
Indicates that an entity has access to a runway by means of a specified connecting route, facility, or intermediary.
- 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_69b34542fd908190b11b08faad8decfd |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b3514dc588819086a4c6d585c1b5b1 |
completed | March 12, 2026, 11:50 p.m. |
| PD | Predicate disambiguation | batch_69b34f4e13fc8190a42c519f37959d27 |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:13 p.m.