Triple
T29176417
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yuułuʔiłʔatḥ Government |
E739623
|
entity |
| Predicate | ethnicGroupFamily |
P178601
|
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: [Yuułuʔiłʔatḥ Government, ethnicGroupFamily, Nuu-chah-nulth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ethnicGroupFamily Context triple: [Yuułuʔiłʔatḥ Government, ethnicGroupFamily, Nuu-chah-nulth]
-
A.
familyGroup
Indicates that multiple entities are related to each other as members of the same family unit or household.
-
B.
familyOf
Indicates a familial relationship exists between the entities, such as by blood, marriage, or adoption.
-
C.
familyType
Indicates the specific familial relationship or category that characterizes how the related entities are connected as family.
-
D.
familyAlliance
Indicates a cooperative or supportive relationship formed between families, often involving mutual obligations, shared interests, or joint actions.
-
E.
globalFamily
Indicates a familial or kinship relationship that extends across national or geographic boundaries, connecting family members living in different parts of the world.
- 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_69f07cb74c2c8190ad396487fcb4fde6 |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69f7117e55908190a67105e92bc4830f |
completed | May 3, 2026, 9:12 a.m. |
| PD | Predicate disambiguation | batch_69f70f380690819090cc34763ba460ed |
completed | May 3, 2026, 9:02 a.m. |
| PDg | Predicate description generation | batch_69f7117cf2188190b29e36fc1e342c60 |
completed | May 3, 2026, 9:12 a.m. |
Created at: April 28, 2026, 11:55 a.m.