Triple

T20395338
Position Surface form Disambiguated ID Type / Status
Subject Hanis Coos E500187 entity
Predicate hasPeopleName P116331 FINISHED
Object Coos 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: Coos | Statement: [Hanis Coos, hasPeopleName, Coos]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Coos
Context triple: [Hanis Coos, hasPeopleName, Coos]
  • A. Miluk Coos
    Miluk Coos is a subgroup of the Coos people, an Indigenous community traditionally inhabiting the southern Oregon coast.
  • B. Coosan chosen
    Coosan is a small family of Native American languages traditionally spoken along the southern Oregon coast by the Coos peoples.
  • C. Tillamook
    Tillamook refers to a Native American people of the Oregon Coast, historically known for their distinct Salishan language and cultural ties to the coastal and riverine environments of the region.
  • D. Alsea
    Alsea refers to a Native American people and their ancestral language from the central Oregon coast, whose descendants are among the member groups of the Confederated Tribes of Siletz Indians.
  • E. Clatsop
    Clatsop are a Native American people of the Pacific Northwest Coast, traditionally living near the mouth of the Columbia River in what is now northwestern Oregon.
  • 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_69e0b4a71ebc8190b153a36c738730f4 completed April 16, 2026, 10:06 a.m.
NER Named-entity recognition batch_69e67912d7948190ac2fda8ce95e5c70 completed April 20, 2026, 7:05 p.m.
Created at: April 16, 2026, 11:28 a.m.