Triple
T29176857
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Regional District of Nanaimo |
E739636
|
entity |
| Predicate | inCanadianRegion |
P98804
|
FINISHED |
| Object | Vancouver Island and Coast |
—
|
NE NERFINISHED |
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: Vancouver Island and Coast | Statement: [Regional District of Nanaimo, inCanadianRegion, Vancouver Island and Coast]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inCanadianRegion Context triple: [Regional District of Nanaimo, inCanadianRegion, Vancouver Island and Coast]
-
A.
regionCanada
chosen
Indicates that an entity is located in, associated with, or pertains to the geographic region of Canada.
-
B.
inCanadianProvince
Indicates that one entity is located within, or is a part of, a specified Canadian province.
-
C.
regionCanadianSide
Indicates that the specified region is located on the Canadian side of a border or boundary.
-
D.
includesCanadianTerritoryPartially
Indicates that one entity geographically encompasses part, but not all, of the territory of Canada.
-
E.
usedInCanadianProvince
Indicates that something is utilized, applied, or in operation within the jurisdiction of a Canadian province.
- 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_69f07cb74c2c8190ad396487fcb4fde6 |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69f6634101ac8190b1d363da1b98b5f4 |
completed | May 2, 2026, 8:49 p.m. |
| PD | Predicate disambiguation | batch_69f65c24f8b48190af81b575f3c15be5 |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 28, 2026, 11:55 a.m.