Triple

T3649136
Position Surface form Disambiguated ID Type / Status
Subject Chimariko language E77374 entity
Predicate hasEndonym P1435 FINISHED
Object Chimariko E408928 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: Chimariko | Statement: [Chimariko language, hasEndonym, Chimariko]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Chimariko
Context triple: [Chimariko language, hasEndonym, Chimariko]
  • A. Chimariko chosen
    Chimariko is an extinct Native American language once spoken by the Chimariko people in northwestern California.
  • B. Machimura
    Machimura is a Japanese surname most notably associated with Nobutaka Machimura, a prominent Liberal Democratic Party politician and former foreign minister of Japan.
  • C. Shimotsuki
    Shimotsuki was a Japanese destroyer of the Imperial Japanese Navy that served in World War II before being sunk in late 1944.
  • D. Marichi
    Marichi is a revered Vedic sage (one of the Saptarishi) regarded as a mind-born son of Brahma and an important progenitor in Hindu cosmology.
  • E. Koromo
    Koromo was the former name of what is now Toyota City in Aichi Prefecture, Japan, historically known as a regional center before becoming synonymous with the Toyota automobile company.
  • 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_69ad85de1b988190a45f8dbfebc806fc completed March 8, 2026, 2:21 p.m.
NER Named-entity recognition batch_69adc38c22548190a271a69fb832a5a8 completed March 8, 2026, 6:44 p.m.
NED1 Entity disambiguation (via context triple) batch_69b56b316140819089c90f3e2bd81ad8 completed March 14, 2026, 2:05 p.m.
Created at: March 8, 2026, 3:24 p.m.