Triple

T15163399
Position Surface form Disambiguated ID Type / Status
Subject Awaswas E362271 entity
Predicate relatedTo P37 FINISHED
Object Rumsen language E370144 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: Rumsen language | Statement: [Awaswas, relatedTo, Rumsen language]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Rumsen language
Context triple: [Awaswas, relatedTo, Rumsen language]
  • A. Rumsen language chosen
    Rumsen language is an extinct Ohlone (Costanoan) Native American language formerly spoken in the Monterey Bay area of California.
  • B. Chumburung language
    The Chumburung language is a Niger-Congo language spoken primarily by the Chumburung people in Ghana.
  • C. Rarámuri language
    The Rarámuri language is an indigenous Uto-Aztecan language spoken by the Tarahumara (Rarámuri) people of northern Mexico.
  • D. Umphai language
    The Umphai language is a lesser-known Tai language spoken by an ethnic minority community in Southeast Asia, classified within the Waic branch of the Tai language family.
  • E. Amuesha language
    The Amuesha language, also known as Yanesha', is an Arawakan language spoken by the Yanesha' people of the central Peruvian Amazon.
  • 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.