Triple
T17259846
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Central Pomo |
E418980
|
entity |
| Predicate | closelyRelatedTo |
P37
|
FINISHED |
| Object | Northern Pomo |
—
|
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: Northern Pomo | Statement: [Central Pomo, closelyRelatedTo, Northern Pomo]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Northern Pomo Context triple: [Central Pomo, closelyRelatedTo, Northern Pomo]
-
A.
Northern Pomo
chosen
Northern Pomo is an extinct Pomoan language variety once spoken by the Pomo people in northern California.
-
B.
Eastern Pomo
Eastern Pomo is a now-extinct Pomoan language variety once spoken by the Eastern Pomo people of Northern California.
-
C.
Western Pomoan
Western Pomoan is a branch of the Pomoan language family comprising several closely related indigenous languages traditionally spoken in northern California.
-
D.
Southeastern Pomo
Southeastern Pomo is one of the distinct Pomoan languages traditionally spoken by the Pomo people of Northern California.
-
E.
Southwestern Pomo
Southwestern Pomo, also known as Kashaya Pomo, is a Pomoan language traditionally spoken by the Kashaya people of the Sonoma County coastal region in Northern California.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d886d9ab108190b70edd8d17aa1204 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e42e6fa940819089046d1b12dede2c |
completed | April 19, 2026, 1:22 a.m. |
Created at: April 10, 2026, 5:39 a.m.