Triple

T3703597
Position Surface form Disambiguated ID Type / Status
Subject Gorontalo E80838 entity
Predicate localLanguage P1252 FINISHED
Object Atinggola language E155818 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: Atinggola language | Statement: [Gorontalo, localLanguage, Atinggola language]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Atinggola language
Context triple: [Gorontalo, localLanguage, Atinggola language]
  • A. Atinggola language chosen
    The Atinggola language is an Austronesian language of the Gorontalo–Mongondow group spoken by a small community in northern Sulawesi, Indonesia.
  • B. Kalanguya language
    The Kalanguya language is an Austronesian language spoken by the Kalanguya people in the northern Luzon highlands of the Philippines.
  • C. Tontemboan language
    The Tontemboan language is an Austronesian language spoken by the Tontemboan people of North Sulawesi, Indonesia, and is one of the traditional Minahasan languages of the region.
  • D. Attié language
    The Attié language is a Niger-Congo language spoken primarily by the Attié people of southern Côte d'Ivoire.
  • E. Gonja language
    The Gonja language is a Gur language spoken primarily by the Gonja people in northern Ghana.
  • 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_69ad8b1793888190a5f70e4b21dc05a1 completed March 8, 2026, 2:43 p.m.
NER Named-entity recognition batch_69adc54aaac88190b775dba2513b6d4a completed March 8, 2026, 6:51 p.m.
NED1 Entity disambiguation (via context triple) batch_69b4cdf822348190bf95f7d119c6265a completed March 14, 2026, 2:54 a.m.
Created at: March 8, 2026, 3:33 p.m.