Triple

T21625762
Position Surface form Disambiguated ID Type / Status
Subject Wik-Mungkan E533696 entity
Predicate hasAlternativeName P39 FINISHED
Object Wik-Mungkn 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: Wik-Mungkn | Statement: [Wik-Mungkan, hasAlternativeName, Wik-Mungkn]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Wik-Mungkn
Context triple: [Wik-Mungkan, hasAlternativeName, Wik-Mungkn]
  • A. Wik-Mungkan chosen
    Wik-Mungkan is an Aboriginal Australian language traditionally spoken by the Wik peoples of western Cape York Peninsula in Queensland.
  • B. Wou-Ki
    Wou-Ki is the given name of Zao Wou-Ki, a renowned Chinese-French painter known for his lyrical abstract works.
  • C. Muye
    Muye was the site of an ancient Chinese battlefield where the Zhou forces decisively overthrew the Shang dynasty.
  • D. Menkorer
    Menkorer is the historical name of the Ethiopian town now known as Debre Markos, a regional center in northwestern Ethiopia.
  • E. Wangkatha
    Wangkatha is an Aboriginal Australian language variety spoken by the Wangkatha people of the Goldfields region in Western Australia.
  • 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_69e0c464fba881908d0ff2ac80511ce1 completed April 16, 2026, 11:13 a.m.
NER Named-entity recognition batch_69ef52131f2c8190b9966adf43a0fe4f completed April 27, 2026, 12:09 p.m.
Created at: April 16, 2026, 6:34 p.m.