Triple
T33352199
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nock-ay-det-klinne |
E853974
|
entity |
| Predicate | broaderEthnicGroup |
P97190
|
FINISHED |
| Object | Western Apache |
—
|
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: Western Apache | Statement: [Nock-ay-det-klinne, broaderEthnicGroup, Western Apache]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: broaderEthnicGroup Context triple: [Nock-ay-det-klinne, broaderEthnicGroup, Western Apache]
-
A.
otherEthnicGroup
Indicates that one entity belongs to a different ethnic group than the other entity.
-
B.
ethnicGroupInFocus
Indicates that a particular ethnic group is the primary subject or focal point within a given context, relation, or description.
-
C.
broaderIndigenousGrouping
chosen
Indicates that one indigenous group is a broader, more inclusive grouping that encompasses another, more specific indigenous group.
-
D.
involvedEthnicGroup
Indicates that a particular ethnic group participates in, is affected by, or is otherwise associated with the referenced event, situation, or entity.
-
E.
commonInEthnicGroup
Indicates that something (such as a trait, condition, or characteristic) occurs with notable frequency within a specified ethnic group.
- 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_69f3496acbc8819099fd0305ecc42080 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7221dc9a88190bb8194fcc29c42bc |
completed | May 3, 2026, 10:23 a.m. |
| PD | Predicate disambiguation | batch_69f72153a9188190b02adc84e1be4af8 |
completed | May 3, 2026, 10:20 a.m. |
Created at: May 1, 2026, 1:34 a.m.