Triple

T9560870
Position Surface form Disambiguated ID Type / Status
Subject Yawuru E230667 entity
Predicate language P15 FINISHED
Object Yawuru language E647962 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: Yawuru language | Statement: [Yawuru, language, Yawuru language]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Yawuru language
Context triple: [Yawuru, language, Yawuru language]
  • A. Yawalapiti language
    The Yawalapiti language is an Arawakan language spoken by the Yawalapiti people of Brazil’s Upper Xingu region in the Amazon.
  • B. Yugambeh language chosen
    The Yugambeh language is an Australian Aboriginal language traditionally spoken by the Yugambeh people of southeast Queensland and northern New South Wales.
  • C. Darumbal language
    The Darumbal language is an Australian Aboriginal language traditionally spoken by the Darumbal people of central Queensland, particularly around the Rockhampton region.
  • D. Warao language
    The Warao language is an indigenous language isolate spoken by the Warao people of northeastern Venezuela and nearby regions, particularly in the Orinoco Delta.
  • E. Juruna language
    The Juruna language is an indigenous Tupian language spoken by the Juruna (Yudjá) people of the Xingu region in Brazil.
  • 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_69ca847e53a88190a60eed7e02257f10 completed March 30, 2026, 2:11 p.m.
NER Named-entity recognition batch_69cd994bde0c8190afcba5cb8fa8b984 completed April 1, 2026, 10:16 p.m.
NED1 Entity disambiguation (via context triple) batch_69d1529b4974819096e26153c60bf05c completed April 4, 2026, 6:04 p.m.
Created at: March 30, 2026, 8:03 p.m.