Triple
T7539595
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Samos International Airport |
E178238
|
entity |
| Predicate | approachRequiresVisualManeuvering |
P31136
|
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: [Samos International Airport, approachRequiresVisualManeuvering, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approachRequiresVisualManeuvering Context triple: [Samos International Airport, approachRequiresVisualManeuvering, true]
-
A.
approachControl
Indicates that one entity moves closer to another entity in a deliberate or controlled manner.
-
B.
hasApproachControl
Indicates that one entity exercises approach control authority or responsibility over another entity, typically managing its approach phase or access.
-
C.
hasVisualApproachProcedures
chosen
Indicates that an entity has associated visual approach procedures defined or available for use.
-
D.
hasApproachHeading
Indicates that an entity follows or is aligned with a specified heading or direction when making an approach.
-
E.
hasApproachRoad
Indicates that one entity is connected to or accessed by another entity via an approach road leading to it.
- 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_69c69f2be3888190a6667a27f8f195e9 |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f87280f0819097d4ffc2e1b62cf8 |
completed | March 27, 2026, 9:36 p.m. |
| PD | Predicate disambiguation | batch_69c6f4d8eedc81908c1ae421e0e63798 |
completed | March 27, 2026, 9:21 p.m. |
Created at: March 27, 2026, 3:48 p.m.