Triple

T15520803
Position Surface form Disambiguated ID Type / Status
Subject Bajan E368960 entity
Predicate hasSubstrateInfluence P33392 FINISHED
Object Akan E54191 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: Akan | Statement: [Bajan, hasSubstrateInfluence, Akan]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Akan
Context triple: [Bajan, hasSubstrateInfluence, Akan]
  • A. Akan chosen
    Akan is a major Central Tano language spoken primarily in Ghana and parts of Côte d’Ivoire, serving as a key lingua franca and cultural language for the Akan people.
  • B. Akena
    Akena is a Ugandan surname notably borne by politician Jimmy Akena, associated with the country’s contemporary political landscape.
  • C. Osanobua
    Osanobua is the supreme creator god and central deity in the traditional religion and cosmology of the Edo people of Nigeria.
  • D. Ayan
    Ayan is a remote settlement in Russia’s Khabarovsk Krai, known as a small port village on the Sea of Okhotsk.
  • E. Ayan
    Ayan is a 2009 Tamil-language action thriller film starring Suriya, known for its smuggling-centric plot and commercial success.
  • 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_69d85a1794cc8190b0b428716296e63e completed April 10, 2026, 2:01 a.m.
NER Named-entity recognition batch_69e0403543188190abac49d2b9decb89 completed April 16, 2026, 1:49 a.m.
NED1 Entity disambiguation (via context triple) batch_69ff3d54ea5c8190b3b220ad10ba8f40 completed May 9, 2026, 1:57 p.m.
Created at: April 10, 2026, 4:04 a.m.