Triple

T11501975
Position Surface form Disambiguated ID Type / Status
Subject Manus people E272684 entity
Predicate traditionalLanguage P6149 FINISHED
Object Likum language E655634 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: Likum language | Statement: [Manus people, traditionalLanguage, Likum language]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Likum language
Context triple: [Manus people, traditionalLanguage, Likum language]
  • A. Likum language chosen
    The Likum language is an Oceanic language spoken in Papua New Guinea’s Admiralty Islands, forming part of the region’s indigenous linguistic diversity.
  • B. Khumi language
    The Khumi language is a lesser-known Tibeto-Burman language spoken primarily by the Khumi people in parts of Myanmar and neighboring regions.
  • C. Kumbewaha language
    The Kumbewaha language is an Austronesian language spoken in Sulawesi, Indonesia, belonging to the Wotu–Wolio subgroup.
  • D. Chumburung language
    The Chumburung language is a Niger-Congo language spoken primarily by the Chumburung people in Ghana.
  • E. Kalanguya language
    The Kalanguya language is an Austronesian language spoken by the Kalanguya people in the northern Luzon highlands of the Philippines.
  • 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_69d6aae2c3748190bed2ea50dfb160dc completed April 8, 2026, 7:22 p.m.
NER Named-entity recognition batch_69d85de55cbc8190be71c2d03dc044f2 completed April 10, 2026, 2:18 a.m.
NED1 Entity disambiguation (via context triple) batch_69e604bc1d3c81908497f1d19dcc2167 completed April 20, 2026, 10:49 a.m.
Created at: April 8, 2026, 9:36 p.m.