Triple

T15163346
Position Surface form Disambiguated ID Type / Status
Subject Chochenyo E362270 entity
Predicate hasAlternativeName P39 FINISHED
Object Chocheño E362270 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: Chocheño | Statement: [Chochenyo, hasAlternativeName, Chocheño]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Chocheño
Context triple: [Chochenyo, hasAlternativeName, Chocheño]
  • A. Winaray
    Winaray is an Austronesian language spoken primarily in the Eastern Visayas region of the Philippines, particularly in Samar, northern Leyte, and nearby areas.
  • B. Segestani
    The Segestani were an ancient Illyrian tribe that inhabited the region around the city of Siscia in what is now central Croatia.
  • C. Lenguazaque
    Lenguazaque is a small municipality in the Cundinamarca Department of Colombia, situated on the Altiplano Cundiboyacense and known historically for its coal mining activities.
  • D. Chiac
    Chiac is a distinctive mixed French-English dialect spoken primarily by Acadian communities in southeastern New Brunswick, Canada.
  • E. Chochenyo chosen
    Chochenyo is an indigenous Ohlone language traditionally spoken in the East Bay region of the San Francisco Bay Area in California.
  • 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_69d85a087b7c81908baa94a53dac8d68 completed April 10, 2026, 2:01 a.m.
NER Named-entity recognition batch_69e0064b21ac81908b793bdbd741bcd8 completed April 15, 2026, 9:42 p.m.
NED1 Entity disambiguation (via context triple) batch_69febffc94e48190844e226c245a9ce3 completed May 9, 2026, 5:02 a.m.
Created at: April 10, 2026, 3:08 a.m.