Triple

T19706034
Position Surface form Disambiguated ID Type / Status
Subject Pichillancahue-Turbio glacier E473215 entity
Predicate hasLanguageOfToponym P24399 FINISHED
Object Mapudungun 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: Mapudungun | Statement: [Pichillancahue-Turbio glacier, hasLanguageOfToponym, Mapudungun]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Mapudungun
Context triple: [Pichillancahue-Turbio glacier, hasLanguageOfToponym, Mapudungun]
  • A. Mapudungun chosen
    Mapudungun is an indigenous language of South America spoken primarily by the Mapuche people in Chile and Argentina.
  • B. Puel Mapu
    Puel Mapu is the eastern portion of the ancestral Mapuche territory, located mainly in what is now Argentina.
  • C. Mazabuka
    Mazabuka is a town in southern Zambia known for its sugar industry and agricultural production.
  • D. Mabasa
    Mabasa is a barangay (village-level administrative division) within the municipality of Argao in Cebu, Philippines.
  • E. Mapusa
    Mapusa is a bustling commercial town in North Goa, India, known as a major market and transport hub near the popular beaches of the state.
  • 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_69d8e516dd048190a0b6c93ea3e71f58 completed April 10, 2026, 11:55 a.m.
NER Named-entity recognition batch_69e642ba4bd08190b016b8c6664079c4 completed April 20, 2026, 3:14 p.m.
Created at: April 10, 2026, 1:46 p.m.