Triple
T29050091
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Village of Daajing Giids Council |
E735242
|
entity |
| Predicate | formerNameOfJurisdiction |
P196621
|
FINISHED |
| Object | Queen Charlotte |
—
|
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: Queen Charlotte | Statement: [Village of Daajing Giids Council, formerNameOfJurisdiction, Queen Charlotte]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formerNameOfJurisdiction Context triple: [Village of Daajing Giids Council, formerNameOfJurisdiction, Queen Charlotte]
-
A.
formerNameOfDistrict
Indicates that one district previously had a different official name, which is the value linked by this predicate.
-
B.
formerNameOfProvince
Indicates that one name was previously used as the official name of a province before being replaced by another name.
-
C.
formerNameOfRegion
Indicates that one name was previously used for a region that is now known by a different name.
-
D.
formerJurisdictionType
Indicates the type or category of jurisdiction that an entity previously held but no longer holds.
-
E.
formerNameOfAreaWithin
Indicates that one area previously had a different name while remaining within the same larger encompassing area.
- 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_69f077e64b88819094d37bdbca8191b3 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69fe5ec9028081909ae3d6fbe2f4cbbc |
completed | May 8, 2026, 10:08 p.m. |
| PD | Predicate disambiguation | batch_69fe5e1d715881909fc516fafc707644 |
completed | May 8, 2026, 10:05 p.m. |
| PDg | Predicate description generation | batch_69fe5ec84910819094cb15269ace7c51 |
completed | May 8, 2026, 10:08 p.m. |
Created at: April 28, 2026, 10:07 a.m.