Triple

T17475141
Position Surface form Disambiguated ID Type / Status
Subject Southeastern Pomo E425519 entity
Predicate hasAncestor P369 FINISHED
Object Proto-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: Proto-Pomo | Statement: [Southeastern Pomo, hasAncestor, Proto-Pomo]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Proto-Pomo
Context triple: [Southeastern Pomo, hasAncestor, Proto-Pomo]
  • A. Proto-Pomo chosen
    Proto-Pomo is the reconstructed common ancestor language of the Pomoan language family traditionally spoken in Northern California.
  • B. Pomo
    The Pomo are a Native American people indigenous to what is now Northern California, traditionally known for their intricate basketry and diverse local dialects.
  • C. Proto-Min
    Proto-Min is the reconstructed common ancestor of the Min group of Sinitic languages, representing an early stage of Chinese spoken in southeastern China before significant later divergences.
  • D. Proto-Daju
    Proto-Daju is the reconstructed ancestral language from which the modern Daju languages, including Daju Mongo, are derived.
  • E. Proto-Koman
    Proto-Koman is the reconstructed ancestral language from which the modern Koman languages of the Nilo-Saharan family are derived.
  • 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.