Triple
T29726055
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vancouver Harbour Flight Centre seaplane terminal |
E752181
|
entity |
| Predicate | waterAerodromeType |
P182839
|
FINISHED |
| Object | seaplane base |
—
|
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: seaplane base | Statement: [Vancouver Harbour Flight Centre seaplane terminal, waterAerodromeType, seaplane base]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: waterAerodromeType Context triple: [Vancouver Harbour Flight Centre seaplane terminal, waterAerodromeType, seaplane base]
-
A.
waterAirport
Indicates that an airport is located on or adjacent to a body of water and is designed to support water-based aircraft operations.
-
B.
airportIsland
Indicates that an airport is located on, or associated with, an island.
-
C.
hasSeaplaneFacilities
Indicates that a location or facility provides infrastructure and services specifically for the operation, docking, or handling of seaplanes.
-
D.
hasSeaplaneFacilitiesNearby
Indicates that the subject has seaplane facilities located in its nearby vicinity.
-
E.
navigationAidType
Indicates the specific kind or category of navigation aid associated with an entity.
- F. None of above. chosen
Provenance (4 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_69f0d628c00c8190ab5ee7e423d7ec3c |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f794f24e588190965e39b77534d53f |
completed | May 3, 2026, 6:33 p.m. |
| PD | Predicate disambiguation | batch_69f791033d288190b118029fe412b9c9 |
completed | May 3, 2026, 6:16 p.m. |
| PDg | Predicate description generation | batch_69f791cad5e08190a8a04ca283dbecaa |
completed | May 3, 2026, 6:19 p.m. |
Created at: April 28, 2026, 7:39 p.m.