Triple

T6981830
Position Surface form Disambiguated ID Type / Status
Subject Shompen people E161864 entity
Predicate language P15 FINISHED
Object Shompen language E105735 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: Shompen language | Statement: [Shompen people, language, Shompen language]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Shompen language
Context triple: [Shompen people, language, Shompen language]
  • A. Shompen language chosen
    Shompen language is an endangered and poorly documented Austroasiatic language spoken by the indigenous Shompen people of Great Nicobar Island in India.
  • B. Rumsen language
    Rumsen language is an extinct Ohlone (Costanoan) Native American language formerly spoken in the Monterey Bay area of California.
  • C. Amuesha language
    The Amuesha language, also known as Yanesha', is an Arawakan language spoken by the Yanesha' people of the central Peruvian Amazon.
  • D. Chumburung language
    The Chumburung language is a Niger-Congo language spoken primarily by the Chumburung people in Ghana.
  • E. Pokomo language
    The Pokomo language is a Bantu language spoken primarily by the Pokomo people along Kenya’s Tana River.
  • 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_69c68855dc0481909b4c7e9e9ed273db completed March 27, 2026, 1:38 p.m.
NER Named-entity recognition batch_69c6db6d3f3c8190b0121f7934440c34 completed March 27, 2026, 7:33 p.m.
NED1 Entity disambiguation (via context triple) batch_69c761c0ecd88190a684392aa6daf267 completed March 28, 2026, 5:06 a.m.
Created at: March 27, 2026, 2:31 p.m.