Triple
T26604300
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nutashkuan First Nation |
E667725
|
entity |
| Predicate | hasCollectiveNameInLanguage |
P167262
|
FINISHED |
| Object | Innu-aimun |
—
|
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: Innu-aimun | Statement: [Nutashkuan First Nation, hasCollectiveNameInLanguage, Innu-aimun]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCollectiveNameInLanguage Context triple: [Nutashkuan First Nation, hasCollectiveNameInLanguage, Innu-aimun]
-
A.
hasCollectiveNameInSwedish
Indicates that a group or collection is referred to by a specific collective name in the Swedish language.
-
B.
hasNameInLocalLanguage
Indicates that an entity is associated with a name expressed in the local or native language of a given context or region.
-
C.
collectiveNameLanguageFamily
Indicates that a term is the collective name used to refer to a particular language family.
-
D.
hasFamilyNameInLanguage
Indicates that an entity has a specific family name as expressed or written in a particular language.
-
E.
hasLinguisticName
chosen
Indicates that an entity is associated with a specific linguistic name or label used to refer to it in a language.
- 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_69ee9cfd20348190bb1255d2603efb7a |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69fdfbafe32081909c62653ff4fc155c |
completed | May 8, 2026, 3:05 p.m. |
| PD | Predicate disambiguation | batch_69fdf64db4a881908f8250e24ae3cefb |
completed | May 8, 2026, 2:42 p.m. |
Created at: April 27, 2026, 2:13 a.m.