Triple
T17191875
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kashaya Pomo |
E417246
|
entity |
| Predicate | closelyRelatedTo |
P37
|
FINISHED |
| Object | Southern Pomo |
E149722
|
NE 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: Southern Pomo | Statement: [Kashaya Pomo, closelyRelatedTo, Southern Pomo]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Southern Pomo Context triple: [Kashaya Pomo, closelyRelatedTo, Southern Pomo]
-
A.
Southern Pomo
chosen
Southern Pomo is a Native American people indigenous to what is now Northern California, traditionally inhabiting areas around the Russian River and nearby coastal regions.
-
B.
Southeastern Pomo
Southeastern Pomo is one of the distinct Pomoan languages traditionally spoken by the Pomo people of Northern California.
-
C.
Central Pomo
Central Pomo is an indigenous Pomoan language variety traditionally spoken by the Pomo people of Northern California.
-
D.
Eastern Pomo
Eastern Pomo is a now-extinct Pomoan language variety once spoken by the Eastern Pomo people of Northern California.
-
E.
Northern Pomo
Northern Pomo is an extinct Pomoan language variety once spoken by the Pomo people in northern California.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d886d6ba8c819093215917b3d01689 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e42d9ae6d88190aaca9fbb32334d65 |
completed | April 19, 2026, 1:19 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a01c1e78d788190adb16779da468a3d |
completed | May 11, 2026, 11:47 a.m. |
Created at: April 10, 2026, 5:38 a.m.