Triple
T28534751
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Velana International Airport |
E722131
|
entity |
| Predicate | hasSeaplaneTerminal |
P37751
|
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: [Velana International Airport, hasSeaplaneTerminal, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSeaplaneTerminal Context triple: [Velana International Airport, hasSeaplaneTerminal, yes]
-
A.
hasSeaplaneFacilities
chosen
Indicates that a location or facility provides infrastructure and services specifically for the operation, docking, or handling of seaplanes.
-
B.
hasSeaplaneFacilitiesNearby
Indicates that the subject has seaplane facilities located in its nearby vicinity.
-
C.
hasHeliport
Indicates that an entity possesses or is equipped with a heliport facility for helicopter landing and takeoff.
-
D.
hasLandingFacilities
Indicates that a location or structure is equipped with facilities that allow aircraft or other vehicles to land there.
-
E.
hasAirportAccessTo
Indicates that one location or entity has direct access to another via an airport connection or service.
- 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_69f01a5d7ec88190ada2d5be7c06c35d |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69fd864235b481908738dbb69556bc62 |
completed | May 8, 2026, 6:44 a.m. |
| PD | Predicate disambiguation | batch_69fd8373b6bc819091c554f29ee17fec |
completed | May 8, 2026, 6:32 a.m. |
Created at: April 28, 2026, 3:31 a.m.