Triple
T21309349
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bearskin Lake First Nation |
E525286
|
entity |
| Predicate | hasPrimaryCommunityName |
P37686
|
FINISHED |
| Object | Bearskin Lake |
—
|
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: Bearskin Lake | Statement: [Bearskin Lake First Nation, hasPrimaryCommunityName, Bearskin Lake]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrimaryCommunityName Context triple: [Bearskin Lake First Nation, hasPrimaryCommunityName, Bearskin Lake]
-
A.
hasCommunalAppellation
chosen
Indicates that an entity shares a common or collective name or designation with a group or community.
-
B.
hasPrimaryEthnonym
Indicates that an entity is associated with its main or most commonly used ethnonym (ethnic group name) as its primary designation.
-
C.
hasTribeCommonName
Indicates that two entities are related by the commonly used (vernacular) name of a tribe.
-
D.
hasPrimarySectOfLocalCommunity
Indicates that a local community is primarily associated with or predominantly follows a particular religious sect.
-
E.
hasCommunityIn
Indicates that a community is present, active, or established within a specified location, platform, or context.
- 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_69e0b518b8948190ad69cf9a8784d397 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e75aa916548190a11f8bb4255e3fed |
completed | April 21, 2026, 11:08 a.m. |
| PD | Predicate disambiguation | batch_69e61612ab748190a72b8703b938abcb |
completed | April 20, 2026, 12:03 p.m. |
Created at: April 16, 2026, 4:06 p.m.