Triple

T4272380
Position Surface form Disambiguated ID Type / Status
Subject Pomo people E96968 entity
Predicate hasLanguage P15 FINISHED
Object Northern Pomo language E417245 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: Northern Pomo language | Statement: [Pomo people, hasLanguage, Northern Pomo language]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Northern Pomo language
Context triple: [Pomo people, hasLanguage, Northern Pomo language]
  • A. 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.
  • B. Southeastern Pomo
    Southeastern Pomo is one of the distinct Pomoan languages traditionally spoken by the Pomo people of Northern California.
  • C. Miwok languages
    Miwok languages are a group of closely related Native American languages traditionally spoken by the Miwok peoples of central and northern California.
  • D. Northern Pomo chosen
    Northern Pomo is an extinct Pomoan language variety once spoken by the Pomo people in northern California.
  • E. Eastern Pomo
    Eastern Pomo is a now-extinct Pomoan language variety once spoken by the Eastern Pomo people of 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_69b34543f06c8190915ebb1a4574ffa9 completed March 12, 2026, 10:59 p.m.
NER Named-entity recognition batch_69b34ffce3d8819083d2278547fa52c1 completed March 12, 2026, 11:45 p.m.
NED1 Entity disambiguation (via context triple) batch_69b5d0665b548190b6a26cda97cb7f9b completed March 14, 2026, 9:17 p.m.
Created at: March 12, 2026, 11:07 p.m.