Triple
T8664402
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nanaimo Harbour Water Airport |
E205628
|
entity |
| Predicate | isWaterAirport |
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: [Nanaimo Harbour Water Airport, isWaterAirport, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isWaterAirport Context triple: [Nanaimo Harbour Water Airport, isWaterAirport, yes]
-
A.
isCoastalAirport
Indicates that an airport is located on or very near a coastline, typically adjacent to a sea or ocean.
-
B.
isCivilAirport
Indicates that an airport is designated and used primarily for civilian (non-military) aviation operations.
-
C.
isMajorAirportOnIsland
Indicates that the airport is classified as a major airport and is geographically located on an island.
-
D.
hasSeaplaneFacilities
chosen
Indicates that a location or facility provides infrastructure and services specifically for the operation, docking, or handling of seaplanes.
-
E.
isDeepWaterPort
Indicates that a port has sufficiently deep water to accommodate large, heavily loaded vessels without grounding.
- 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_69ca83516ae88190aefe034b3bc589e3 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc48a0ae108190b33dadcc3cb18949 |
completed | March 31, 2026, 10:20 p.m. |
| PD | Predicate disambiguation | batch_69cc4564e018819081036722f3e42a71 |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:30 p.m.