Triple

T7197697
Position Surface form Disambiguated ID Type / Status
Subject Minahasan people E168656 entity
Predicate language P15 FINISHED
Object Ponosakan language E638879 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: Ponosakan language | Statement: [Minahasan people, language, Ponosakan language]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Ponosakan language
Context triple: [Minahasan people, language, Ponosakan language]
  • A. Ponosakan language chosen
    The Ponosakan language is an endangered Austronesian language traditionally spoken by a small community in northern Sulawesi, Indonesia.
  • B. Mikasuki language
    The Mikasuki language is a Native American Muskogean language traditionally spoken by the Miccosukee and Seminole peoples of Florida.
  • C. Pokomo language
    The Pokomo language is a Bantu language spoken primarily by the Pokomo people along Kenya’s Tana River.
  • D. Opokuma language
    The Opokuma language is a Niger-Congo language spoken by the Opokuma subgroup of the Ijaw people in Nigeria’s Niger Delta region.
  • E. Pamona language
    The Pamona language is an Austronesian language spoken by the Pamona people of central Sulawesi, Indonesia.
  • 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_69c68a5376748190bb500f03df86e93e completed March 27, 2026, 1:46 p.m.
NER Named-entity recognition batch_69c6e92a5d288190955f703470e75bf3 completed March 27, 2026, 8:31 p.m.
NED1 Entity disambiguation (via context triple) batch_69c7bfa6be648190950f682eaaeb1a18 completed March 28, 2026, 11:46 a.m.
Created at: March 27, 2026, 2:51 p.m.