Triple

T14066679
Position Surface form Disambiguated ID Type / Status
Subject Taharqa E338492 entity
Predicate successor P78 FINISHED
Object Tantamani E276351 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: Tantamani | Statement: [Taharqa, successor, Tantamani]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Tantamani
Context triple: [Taharqa, successor, Tantamani]
  • A. Tantamani chosen
    Tantamani was a Kushite king of the 25th Dynasty of Egypt, known for his brief attempt to restore Nubian control over Egypt before being driven back by the Assyrians.
  • B. Tangale
    Tangale is a West Chadic language spoken primarily in Gombe State, northeastern Nigeria, by the Tangale people.
  • C. Nganzai
    Nganzai is a local government area in Borno State, northeastern Nigeria, known for its rural communities and impact from the Boko Haram insurgency.
  • D. Tamasopo
    Tamasopo is a small town in the Huasteca Potosina region of San Luis Potosí, Mexico, known for its lush landscapes and popular nearby waterfalls and natural swimming areas.
  • E. Tandi
    Tandi is a small rural settlement located in Makoni District in eastern Zimbabwe.
  • 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_69d81c67ba6c819091935650dfb3b895 completed April 9, 2026, 9:38 p.m.
NER Named-entity recognition batch_69de568b81f08190a571004261c0e8e4 completed April 14, 2026, 3 p.m.
NED1 Entity disambiguation (via context triple) batch_69fcd09db51c8190ab275e68b1aec120 completed May 7, 2026, 5:49 p.m.
Created at: April 9, 2026, 10:21 p.m.