Triple
T36277139
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chumash |
E892838
|
entity |
| Predicate | presentDayTribe |
P25195
|
FINISHED |
| Object | Santa Ynez Band of Chumash Indians |
—
|
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: Santa Ynez Band of Chumash Indians | Statement: [Chumash, presentDayTribe, Santa Ynez Band of Chumash Indians]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: presentDayTribe Context triple: [Chumash, presentDayTribe, Santa Ynez Band of Chumash Indians]
-
A.
presentDayTribalEntity
chosen
Indicates that an entity is recognized as a currently existing (present-day) tribal group or tribal governmental body.
-
B.
presentDayFederallyRecognizedTribe
Indicates that an entity is recognized as a Native American tribe by the federal government in the present day.
-
C.
tribeOrGens
Indicates a relationship where an entity belongs to, is associated with, or is identified as a particular tribe or gens (clan/lineage group).
-
D.
numberOfTribes
Indicates the total count of distinct tribes associated with a given entity or context.
-
E.
ethnicOrTribalBase
Indicates that something is founded on, derived from, or primarily organized around a particular ethnic or tribal group or identity.
- 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_69f76e488f34819083e254dbe288c27a |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fd6a1c1c4881908090053bc359b181 |
completed | May 8, 2026, 4:44 a.m. |
| PD | Predicate disambiguation | batch_69fd696f24d8819091033afacbdaadc5 |
completed | May 8, 2026, 4:41 a.m. |
Created at: May 3, 2026, 4:09 p.m.