Triple

T23333372
Position Surface form Disambiguated ID Type / Status
Subject Konkow Maidu E591505 entity
Predicate hasAutonym P1435 FINISHED
Object Konkow 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: Konkow | Statement: [Konkow Maidu, hasAutonym, Konkow]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Konkow
Context triple: [Konkow Maidu, hasAutonym, Konkow]
  • A. Konkow chosen
    Konkow is a Native American people and their associated language traditionally located in northern California, considered one of the primary branches of the Maiduan language family.
  • B. Boitsfort
    Boitsfort is a locality in the Brussels-Capital Region of Belgium, known for its residential character and proximity to the Sonian Forest.
  • C. Opawa
    Opawa is a riverside suburb of Christchurch, New Zealand, known for its residential character and proximity to the Heathcote River.
  • D. Opawa
    Opawa is the Polish name for the city of Opava, a historical urban center in the Czech Republic’s Silesian region.
  • E. Kekionga
    Kekionga was a major Miami Indian village and strategic stronghold near present-day Fort Wayne, Indiana, that served as a key focal point of conflict between Native American nations and the United States in the late 18th century.
  • 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_69e25d20156c81908c5c53195bd9c738 completed April 17, 2026, 4:17 p.m.
NER Named-entity recognition batch_69f197efd98c819083635a2b8440f3eb completed April 29, 2026, 5:32 a.m.
Created at: April 17, 2026, 5:16 p.m.