Triple

T6510092
Position Surface form Disambiguated ID Type / Status
Subject Mamuju language E150104 entity
Predicate hasNeighborLanguage P16383 FINISHED
Object Mandar language E152161 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: Mandar language | Statement: [Mamuju language, hasNeighborLanguage, Mandar language]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Mandar language
Context triple: [Mamuju language, hasNeighborLanguage, Mandar language]
  • A. Mandar language chosen
    Mandar is an Austronesian language spoken primarily by the Mandar people along the western coast of Sulawesi in Indonesia.
  • B. Mandeali language
    Mandeali language is an Indo-Aryan language spoken primarily in the Mandi region of Himachal Pradesh, India.
  • C. Mambae language
    The Mambae language is an Austronesian language spoken primarily in East Timor, notable for its role in local identity and traditional culture.
  • D. Madi language
    The Madi language is a Central Sudanic language spoken primarily by the Madi people in parts of South Sudan and northern Uganda.
  • E. Mundari
    Mundari is an Austroasiatic Munda language of eastern India, spoken primarily by the Munda people in states such as Jharkhand, Odisha, and West Bengal.
  • 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_69c687ef291081909d437f035eef1cda completed March 27, 2026, 1:36 p.m.
NER Named-entity recognition batch_69c69f398f10819096342f3646cefcc2 completed March 27, 2026, 3:16 p.m.
NED1 Entity disambiguation (via context triple) batch_69c6d50d155c81908b01914db32494d8 completed March 27, 2026, 7:05 p.m.
Created at: March 27, 2026, 1:43 p.m.