Triple

T20166937
Position Surface form Disambiguated ID Type / Status
Subject Yuin people E491846 entity
Predicate traditionalLanguage P6149 FINISHED
Object Dhurga 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: Dhurga language | Statement: [Yuin people, traditionalLanguage, Dhurga language]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Dhurga language
Context triple: [Yuin people, traditionalLanguage, Dhurga language]
  • A. Dhurga language chosen
    The Dhurga language is an Australian Aboriginal language traditionally spoken by the Yuin people of the south coast of New South Wales.
  • B. Dhundari language
    The Dhundari language is an Indo-Aryan language spoken primarily in the Indian state of Rajasthan, closely associated with the Rajasthani dialect continuum.
  • C. Dhanka language
    Dhanka is an Indo-Aryan tribal language variety considered a dialect within the Bhili language group of western India.
  • D. Dhatki language
    Dhatki language is an Indo-Aryan language spoken primarily by the Thari people in the Thar Desert region spanning parts of Pakistan and India.
  • E. Belhare language
    The Belhare language is a Kiranti language of the Sino-Tibetan family spoken by the Belhare community in eastern Nepal.
  • 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_69da6266c6888190bc1a3ecf24814d34 completed April 11, 2026, 3:01 p.m.
NER Named-entity recognition batch_69e66844e49081909b7e9ec2b65cc61d completed April 20, 2026, 5:54 p.m.
Created at: April 11, 2026, 11:35 p.m.