Triple

T8774243
Position Surface form Disambiguated ID Type / Status
Subject Ashanti E208537 entity
Predicate language P15 FINISHED
Object Asante Twi E302237 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: Asante Twi | Statement: [Ashanti, language, Asante Twi]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Asante Twi
Context triple: [Ashanti, language, Asante Twi]
  • A. Asante Twi chosen
    Asante Twi is a major dialect of the Akan language spoken predominantly by the Asante people in Ghana and widely used in education, media, and everyday communication.
  • B. Akuapem Twi
    Akuapem Twi is a major dialect of the Akan language spoken primarily in the Akuapem area of Ghana and widely used in education, media, and religious contexts.
  • C. Akyem Twi
    Akyem Twi is a regional variety of the Akan language spoken primarily by the Akyem people in Ghana.
  • D. Akpafu dialect
    The Akpafu dialect is a regional variety of the Siwu language spoken by the Akpafu people in the Volta Region of Ghana.
  • E. Sefwi language
    The Sefwi language is a Niger-Congo language spoken primarily by the Sefwi people in western 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_69ca835edb4481909b4aafb616dc5eb7 completed March 30, 2026, 2:06 p.m.
NER Named-entity recognition batch_69cc5f2ef3288190988bd69e8a02e741 completed March 31, 2026, 11:56 p.m.
NED1 Entity disambiguation (via context triple) batch_69cf51c760b48190b2138cd2861b2c61 completed April 3, 2026, 5:36 a.m.
Created at: March 30, 2026, 6:41 p.m.