Triple
T8664401
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nanaimo Harbour Water Airport |
E205628
|
entity |
| Predicate | isHarbourAirport |
P83961
|
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, isHarbourAirport, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isHarbourAirport Context triple: [Nanaimo Harbour Water Airport, isHarbourAirport, yes]
-
A.
isCivilAirport
Indicates that an airport is designated and used primarily for civilian (non-military) aviation operations.
-
B.
isPublicAirport
Indicates that an airport is open for use by the general public rather than restricted to private or military operations.
-
C.
hasInternationalAirport
Indicates that a place possesses an airport that handles international flights and services cross-border air traffic.
-
D.
isRegionalAirport
Indicates that an airport serves a specific region or local area rather than functioning as a major national or international hub.
-
E.
isLocatedAtAirportType
Indicates that one entity is situated at, or associated with, an airport of a specified type (e.g., international, regional, military).
- 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_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. |
| PDg | Predicate description generation | batch_69cc46c330bc8190a9b644078881c6ff |
completed | March 31, 2026, 10:12 p.m. |
Created at: March 30, 2026, 6:30 p.m.