Triple

T17805820
Position Surface form Disambiguated ID Type / Status
Subject Komering people E444554 entity
Predicate language P15 FINISHED
Object Komering language 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: Komering language | Statement: [Komering people, language, Komering language]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Komering language
Context triple: [Komering people, language, Komering language]
  • A. Komering language chosen
    The Komering language is an Austronesian language spoken by the Komering people of southern Sumatra, Indonesia.
  • B. Badimaya language
    Badimaya language is an Australian Aboriginal language traditionally spoken by the Yamatji people of Western Australia.
  • C. Berom language
    The Berom language is a Plateau language spoken primarily by the Berom people in Nigeria’s Middle Belt region, especially around Jos in Plateau State.
  • D. Semai language
    The Semai language is an Austroasiatic language spoken by the Semai people, an indigenous Orang Asli group in Peninsular Malaysia.
  • E. Damana language
    The Damana language is an indigenous Chibchan tongue spoken by the Wiwa people of the Sierra Nevada de Santa Marta region in northern Colombia.
  • 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_69d8b9efe370819095cd219b143ae727 completed April 10, 2026, 8:50 a.m.
NER Named-entity recognition batch_69e4880385b48190b8dea0f05dfa1300 completed April 19, 2026, 7:45 a.m.
Created at: April 10, 2026, 10:14 a.m.