Triple

T6098803
Position Surface form Disambiguated ID Type / Status
Subject Bungku language E135942 entity
Predicate closelyRelatedTo P37 FINISHED
Object Tolaki language E135941 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: Tolaki language | Statement: [Bungku language, closelyRelatedTo, Tolaki language]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Tolaki language
Context triple: [Bungku language, closelyRelatedTo, Tolaki language]
  • A. Tolaki language chosen
    The Tolaki language is an Austronesian language spoken by the Tolaki people of southeastern Sulawesi, Indonesia.
  • B. Tolai language
    The Tolai language is an Austronesian language spoken primarily by the Tolai people of East New Britain in Papua New Guinea.
  • C. Touo language
    Touo is an Oceanic language spoken by a small community in the Solomon Islands, noted for its distinct phonology and limited number of speakers.
  • D. Lakalai language
    The Lakalai language is an Austronesian language spoken by the Lakalai people of New Britain in Papua New Guinea.
  • E. Tofa language
    Tofa is a critically endangered Turkic language traditionally spoken by the Tofa (Tofalars) people of south-central Siberia in Russia.
  • 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_69c0087cd3c48190b459848c72d84eb1 completed March 22, 2026, 3:19 p.m.
NER Named-entity recognition batch_69c05a9a02888190ac201acd14c3fc31 completed March 22, 2026, 9:09 p.m.
NED1 Entity disambiguation (via context triple) batch_69c125475548819086b733a80056eba5 completed March 23, 2026, 11:34 a.m.
Created at: March 22, 2026, 4:13 p.m.