Triple

T7051114
Position Surface form Disambiguated ID Type / Status
Subject Tondano language E163766 entity
Predicate neighboringLanguage P16383 FINISHED
Object Bantik language E155816 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: Bantik language | Statement: [Tondano language, neighboringLanguage, Bantik language]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Bantik language
Context triple: [Tondano language, neighboringLanguage, Bantik language]
  • A. Bantawa language
    The Bantawa language is a Sino-Tibetan language spoken primarily by the Bantawa (Rai) people of eastern Nepal and neighboring regions.
  • B. Balantak language
    The Balantak language is an Austronesian language spoken by the Balantak people of eastern Central Sulawesi, Indonesia.
  • C. Bima language
    Bima language is an Austronesian language spoken primarily on Sumbawa Island in Indonesia, known for its distinct grammar and vocabulary within the region.
  • D. Bintauna language chosen
    The Bintauna language is an Austronesian language spoken by the Bintauna people in North Sulawesi, Indonesia.
  • E. Batangan language
    Batangan language is another name for the Buhid language, an Austronesian language spoken by the Mangyan people of Mindoro in 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_69c6885f598c8190b6b6495c59d8d962 completed March 27, 2026, 1:38 p.m.
NER Named-entity recognition batch_69c6e2500570819087200013d859cfe6 completed March 27, 2026, 8:02 p.m.
NED1 Entity disambiguation (via context triple) batch_69c78891bc5081909db384a35b45df4a completed March 28, 2026, 7:51 a.m.
Created at: March 27, 2026, 2:37 p.m.