Triple
T16894685
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eastern Pomo |
E424266
|
entity |
| Predicate | hasNeighboringLanguage |
P16383
|
FINISHED |
| Object | Central Pomo |
E418980
|
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: Central Pomo | Statement: [Eastern Pomo, hasNeighboringLanguage, Central Pomo]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Central Pomo Context triple: [Eastern Pomo, hasNeighboringLanguage, Central Pomo]
-
A.
Central Pomo
chosen
Central Pomo is an indigenous Pomoan language variety traditionally spoken by the Pomo people of 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.
Southeastern Pomo
Southeastern Pomo is one of the distinct Pomoan languages traditionally spoken by the Pomo people of Northern California.
-
D.
Northern Pomo
Northern Pomo is an extinct Pomoan language variety once spoken by the Pomo people in northern California.
-
E.
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.
- 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_69d889da3e8c8190a2b118f383f0beac |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e3c8d6bfc88190b6b47b89c1135871 |
completed | April 18, 2026, 6:09 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a00dc002fac81908b7628d2add1e2dd |
completed | May 10, 2026, 7:26 p.m. |
Created at: April 10, 2026, 5:29 a.m.