Triple

T9693937
Position Surface form Disambiguated ID Type / Status
Subject Mapudungun E234600 entity
Predicate autonym P1435 FINISHED
Object Mapudungun E234600 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: Mapudungun | Statement: [Mapudungun, autonym, Mapudungun]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Mapudungun
Context triple: [Mapudungun, autonym, Mapudungun]
  • A. Mapudungun chosen
    Mapudungun is an indigenous language of South America spoken primarily by the Mapuche people in Chile and Argentina.
  • B. Mazabuka
    Mazabuka is a town in southern Zambia known for its sugar industry and agricultural production.
  • C. Mwotlap
    Mwotlap is an Oceanic Austronesian language spoken on Mota Lava and nearby islands in northern Vanuatu.
  • D. Umtata
    Umtata is the former name of Mthatha, a town in South Africa’s Eastern Cape that serves as a regional economic and administrative center.
  • E. Mpondo
    The Mpondo are a Southern African ethnic group closely related to the Xhosa, known for their distinct language variety, cultural traditions, and historical kingdom in what is now South Africa’s Eastern Cape.
  • 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_69ca84cb580c8190a7e5f4b3bcdaf2a4 completed March 30, 2026, 2:12 p.m.
NER Named-entity recognition batch_69cd9d348868819083aec7a5da8c455b completed April 1, 2026, 10:33 p.m.
NED1 Entity disambiguation (via context triple) batch_69d1911d33f081908637cbf4c1949bcd completed April 4, 2026, 10:30 p.m.
Created at: March 30, 2026, 8:17 p.m.