Triple

T17475155
Position Surface form Disambiguated ID Type / Status
Subject Southeastern Pomo E425519 entity
Predicate hasAlternativeName P39 FINISHED
Object Southeast 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: Southeast Pomo | Statement: [Southeastern Pomo, hasAlternativeName, Southeast Pomo]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Southeast Pomo
Context triple: [Southeastern Pomo, hasAlternativeName, Southeast 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. 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. 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_69d889dbc2e88190b18ea6115e819258 completed April 10, 2026, 5:25 a.m.
NER Named-entity recognition batch_69e451bb7050819080e3873bcc8a950c completed April 19, 2026, 3:53 a.m.
Created at: April 10, 2026, 5:47 a.m.