Triple
T6411573
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United Auburn Indian Community of the Auburn Rancheria |
E127717
|
entity |
| Predicate | hasTribalMembers |
P70496
|
FINISHED |
| Object | Miwok descendants |
—
|
LITERAL FINISHED |
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: Miwok descendants | Statement: [United Auburn Indian Community of the Auburn Rancheria, hasTribalMembers, Miwok descendants]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTribalMembers Context triple: [United Auburn Indian Community of the Auburn Rancheria, hasTribalMembers, Miwok descendants]
-
A.
hasTribalMembersFrom
Indicates that an entity includes or is composed of members originating from a specified tribe or tribal group.
-
B.
hasTribalCitizens
Indicates that one or more individuals are recognized as official members or citizens of a particular tribe.
-
C.
hasTribalAssociation
Indicates that an entity is affiliated with, belongs to, or is formally associated with a particular tribe or tribal group.
-
D.
hasTribalEnrollment
Indicates that an entity is formally enrolled as a member of a specific tribe or tribal nation.
-
E.
membersPerTribe
Indicates the number of individual members associated with each tribe in the relationship.
- 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_69c0083723d88190b1e37b19df162c08 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c068d0f2b88190af06c208d8c01d07 |
completed | March 22, 2026, 10:10 p.m. |
| PD | Predicate disambiguation | batch_69c060f40ecc8190b1df17b96767675c |
completed | March 22, 2026, 9:36 p.m. |
| PDg | Predicate description generation | batch_69c0623d23448190a75cf5d802fc0a02 |
completed | March 22, 2026, 9:42 p.m. |
Created at: March 22, 2026, 4:41 p.m.