Triple
T29176384
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Toquaht Nation |
E739622
|
entity |
| Predicate | hasEthnoCulturalIdentity |
P156628
|
FINISHED |
| Object | Nuu-chah-nulth |
—
|
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: Nuu-chah-nulth | Statement: [Toquaht Nation, hasEthnoCulturalIdentity, Nuu-chah-nulth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEthnoCulturalIdentity Context triple: [Toquaht Nation, hasEthnoCulturalIdentity, Nuu-chah-nulth]
-
A.
ethnicIdentityOf
chosen
Indicates that one entity is the ethnic identity or affiliation possessed by another entity.
-
B.
hasStrongCulturalIdentity
Indicates that an entity possesses a well-defined, deeply rooted, and strongly maintained sense of belonging to a particular culture or cultural tradition.
-
C.
holderEthnicity
Indicates the ethnic background or group to which the holder of something (e.g., a document, account, or item) belongs.
-
D.
hasEthnicOrRegionalOrigin
Indicates that an entity originates from, or is associated with, a particular ethnic group or geographic region.
-
E.
laterEthnicIdentity
Indicates that an entity’s ethnic identity is associated with or applies to a later period in time relative to some earlier state 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_69f07cb74c2c8190ad396487fcb4fde6 |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69f6cee45590819086e489bfccbe4ac3 |
completed | May 3, 2026, 4:28 a.m. |
| PD | Predicate disambiguation | batch_69f6cc1188708190b8f0f56e595e6057 |
completed | May 3, 2026, 4:16 a.m. |
Created at: April 28, 2026, 11:55 a.m.