Triple

T7405164
Position Surface form Disambiguated ID Type / Status
Subject Shawiya language E170851 entity
Predicate alternateName P39 FINISHED
Object Tachawit E662346 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: Tachawit | Statement: [Shawiya language, alternateName, Tachawit]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Tachawit
Context triple: [Shawiya language, alternateName, Tachawit]
  • A. Tasiwit
    Tasiwit is an alternative name for Siwi, a Berber language spoken in Egypt’s Siwa Oasis.
  • B. Tawu
    Tawu is the indigenous name used by the Tao people, an Austronesian ethnic group native to Orchid Island in Taiwan.
  • C. Tonsawang
    Tonsawang is an Austronesian language spoken by the Tonsawang people in North Sulawesi, Indonesia.
  • D. Tacawit chosen
    Tacawit is another name for the Shawiya language, a Berber (Amazigh) language spoken primarily in the Aurès region of northeastern Algeria.
  • E. Kanowit
    Kanowit is a small riverside town and district in Sarawak, Malaysia, known for its location at the confluence of the Rajang and Kanowit rivers and its ethnically diverse Iban, Chinese, and Malay communities.
  • 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_69c68a6010108190925e5284de022660 completed March 27, 2026, 1:47 p.m.
NER Named-entity recognition batch_69c6f271f1d481909a46d50b13b51a62 completed March 27, 2026, 9:11 p.m.
NED1 Entity disambiguation (via context triple) batch_69c81ed79680819087a56082e968c266 completed March 28, 2026, 6:32 p.m.
Created at: March 27, 2026, 3:10 p.m.