Triple
T11204127
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Funchal Airport |
E265114
|
entity |
| Predicate | hasSeaProximity |
P17623
|
FINISHED |
| Object | runway end close to sea |
—
|
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: runway end close to sea | Statement: [Funchal Airport, hasSeaProximity, runway end close to sea]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSeaProximity Context triple: [Funchal Airport, hasSeaProximity, runway end close to sea]
-
A.
hasNearbyCoast
chosen
Indicates that one location is situated close to a coastline or seashore.
-
B.
hasNearbyWater
Indicates that one entity is located close to a body of water associated with or relevant to another entity.
-
C.
hasIslandNearby
Indicates that one location is situated close to an island in geographic space.
-
D.
stateOnNearestShore
Indicates that an entity is located on the shore that is geographically closest to another specified reference point or entity.
-
E.
nearIsland
Indicates that one entity is located close to or in the vicinity of an island.
- 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_69d6aa9eb9248190b20211772621b4bc |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e8d355c481908fc3d555b596314d |
completed | April 9, 2026, 5:58 p.m. |
| PD | Predicate disambiguation | batch_69d75cf83464819087529d47d025d313 |
completed | April 9, 2026, 8:02 a.m. |
Created at: April 8, 2026, 9:30 p.m.