Triple
T29147457
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Salt Spring Island Electoral Area |
E738809
|
entity |
| Predicate | hasRegionalDistrictCode |
P3446
|
FINISHED |
| Object | CRD |
—
|
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: CRD | Statement: [Salt Spring Island Electoral Area, hasRegionalDistrictCode, CRD]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRegionalDistrictCode Context triple: [Salt Spring Island Electoral Area, hasRegionalDistrictCode, CRD]
-
A.
subregionCodeFor
Indicates that one entity is the code assigned to identify a specific subregion of the other entity.
-
B.
hasCityDistrictCode
Indicates that a city district is associated with a specific identifying code.
-
C.
hasRegionCode
chosen
Indicates that an entity is associated with a specific regional identifier or code.
-
D.
hasRegionalEntity
Indicates that one entity includes, governs, or is associated with another entity that functions as its regional subdivision or component.
-
E.
gridCodeRegion
Indicates a relationship where a specific grid code is associated with, or designates, a particular geographic or administrative region.
- 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_69f07cb46f148190874eb8576a447567 |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69ffbe9e47688190a2692566dc326646 |
completed | May 9, 2026, 11:09 p.m. |
| PD | Predicate disambiguation | batch_69ffbb7b45388190b62cbde5c2d435cd |
completed | May 9, 2026, 10:55 p.m. |
Created at: April 28, 2026, 11:40 a.m.