Triple

T16951369
Position Surface form Disambiguated ID Type / Status
Subject Akateko E411186 entity
Predicate hasGlottologName P6521 FINISHED
Object Akateko E411186 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: Akateko | Statement: [Akateko, hasGlottologName, Akateko]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Akateko
Context triple: [Akateko, hasGlottologName, Akateko]
  • A. Akateko chosen
    Akateko is a Mayan language spoken primarily by the Akateko people in the western highlands of Guatemala and parts of southern Mexico.
  • B. Ake
    Ake is a district in Abeokuta, Nigeria, historically known as a traditional center of Egba leadership and culture.
  • C. Aku Uka
    Aku Uka is the paramount traditional monarch of the Jukun people, historically associated with the ancient Kwararafa kingdom in present-day Taraba State, Nigeria.
  • D. Ipe-Akoko
    Ipe-Akoko is a prominent town in Ondo State, southwestern Nigeria, known as one of the key communities in the Akoko region.
  • E. Akatsi
    Akatsi is a town in southeastern Ghana that serves as a local commercial and administrative center within the Volta Region.
  • 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_69d886c9c9d481909afe222093641cae completed April 10, 2026, 5:12 a.m.
NER Named-entity recognition batch_69e3cfb6e5fc8190b1bd3ad1c2773685 completed April 18, 2026, 6:38 p.m.
NED1 Entity disambiguation (via context triple) batch_6a00d46213b08190b33b48d12bc795d1 completed May 10, 2026, 6:54 p.m.
Created at: April 10, 2026, 5:31 a.m.