Triple

T20395365
Position Surface form Disambiguated ID Type / Status
Subject Miluk Coos E500188 entity
Predicate hasAlternativeName P39 FINISHED
Object Lower 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: Lower Coos | Statement: [Miluk Coos, hasAlternativeName, Lower Coos]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Lower Coos
Context triple: [Miluk Coos, hasAlternativeName, Lower Coos]
  • A. Coosan
    Coosan is a small family of Native American languages traditionally spoken along the southern Oregon coast by the Coos peoples.
  • B. Upper Coquille
    Upper Coquille is an indigenous Athabaskan language historically spoken by the Upper Coquille people of southwestern Oregon in the Pacific Northwest.
  • C. South Fork Coos River
    South Fork Coos River is a tributary stream in southwestern Oregon that flows through the Coast Range forests before joining the main Coos River on its way to Coos Bay and the Pacific Ocean.
  • D. Miluk Coos chosen
    Miluk Coos is a subgroup of the Coos people, an Indigenous community traditionally inhabiting the southern Oregon coast.
  • E. Coos River
    The Coos River is a coastal river in southwestern Oregon that flows through forested terrain to join the Coos Bay estuary near the Pacific Ocean.
  • 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.