Triple

T6774858
Position Surface form Disambiguated ID Type / Status
Subject Nafe language E155130 entity
Predicate hasAlternativeName P39 FINISHED
Object Nguna language E155130 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: Nguna language | Statement: [Nafe language, hasAlternativeName, Nguna language]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Nguna language
Context triple: [Nafe language, hasAlternativeName, Nguna language]
  • A. Nafe (Nguna) language chosen
    The Nafe (Nguna) language is an Oceanic Austronesian language spoken on Nguna Island and nearby areas in central Vanuatu.
  • B. Kalanguya language
    The Kalanguya language is an Austronesian language spoken by the Kalanguya people in the northern Luzon highlands of the Philippines.
  • C. Sanglechi language
    The Sanglechi language is an Eastern Iranian language spoken by a small community in the Sanglech Valley region of Afghanistan and Tajikistan.
  • D. Nngu language
    Nngu is a Bantu language spoken on the northeast coast of Africa, belonging to the Northeast Coast Bantu subgroup.
  • E. Ronga language
    The Ronga language is a Bantu language spoken primarily in southern Mozambique, closely related to Tsonga and used by the Ronga people in the Maputo region.
  • 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_69c68812ef7c819099369f51febb725c completed March 27, 2026, 1:37 p.m.
NER Named-entity recognition batch_69c6d24ddaf08190baffbff991eeb458 completed March 27, 2026, 6:54 p.m.
NED1 Entity disambiguation (via context triple) batch_69c71a803fe08190b4dc32d09e91da07 completed March 28, 2026, 12:02 a.m.
Created at: March 27, 2026, 2:13 p.m.