Triple

T14717148
Position Surface form Disambiguated ID Type / Status
Subject Eggon E345710 entity
Predicate languageSpoken P151 FINISHED
Object Eggon language E345709 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: Eggon language | Statement: [Eggon, languageSpoken, Eggon language]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Eggon language
Context triple: [Eggon, languageSpoken, Eggon language]
  • A. Eggon language chosen
    Eggon language is a Plateau language of the Benue-Congo branch of the Niger-Congo family, spoken primarily by the Eggon people in central Nigeria.
  • B. Gogot language
    The Gogot language is a lesser-known Ethiosemitic language spoken by the Gurage people of Ethiopia.
  • C. Endegen language
    Endegen is an Ethiopian Semitic language belonging to the Gurage branch, spoken by a small community in central Ethiopia.
  • D. Engenni language
    The Engenni language is a Niger-Congo language spoken by the Engenni people in Nigeria’s Niger Delta region.
  • E. Teke-Kega language
    The Teke-Kega language is a Bantu language spoken by the Teke people of Central Africa, primarily in the Republic of the Congo and surrounding regions.
  • 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_69d822e5911c8190ba589f957dbd9ba7 completed April 9, 2026, 10:06 p.m.
NER Named-entity recognition batch_69deb98688f48190b2b19ce7aa06a6db completed April 14, 2026, 10:02 p.m.
NED1 Entity disambiguation (via context triple) batch_69fdf0935f088190b54f2e106532972a completed May 8, 2026, 2:17 p.m.
Created at: April 10, 2026, 1:29 a.m.