Triple
T15536331
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pomoan languages |
E370355
|
entity |
| Predicate | hasMember |
P10
|
FINISHED |
| Object | Southeastern Pomo |
E425519
|
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: Southeastern Pomo | Statement: [Pomoan languages, hasMember, Southeastern Pomo]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Southeastern Pomo Context triple: [Pomoan languages, hasMember, Southeastern Pomo]
-
A.
Southeastern Pomo
chosen
Southeastern Pomo is one of the distinct Pomoan languages traditionally spoken by the Pomo people of Northern California.
-
B.
Northeastern Pomo
Northeastern Pomo is an extinct, historically spoken Native American language variety of the Pomoan family once used in what is now Northern California.
-
C.
Eastern Pomo
Eastern Pomo is a now-extinct Pomoan language variety once spoken by the Eastern Pomo people of Northern California.
-
D.
Southern Pomo
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.
-
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_69d85cc521a08190921fb50319dddc34 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e0442e327c8190b4b879c8a3cd38e3 |
completed | April 16, 2026, 2:06 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ff5f2d4b1c81909ff876289db20803 |
completed | May 9, 2026, 4:22 p.m. |
Created at: April 10, 2026, 4:06 a.m.