Triple

T6296175
Position Surface form Disambiguated ID Type / Status
Subject Hor-Aha E141135 entity
Predicate alsoKnownAs P39 FINISHED
Object Hor-Akha E141135 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: Hor-Akha | Statement: [Hor-Aha, alsoKnownAs, Hor-Akha]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Hor-Akha
Context triple: [Hor-Aha, alsoKnownAs, Hor-Akha]
  • A. Hor-Aha chosen
    Hor-Aha was an early dynastic Egyptian pharaoh, traditionally regarded as one of the first rulers of a unified Egypt and a founder of the First Dynasty.
  • B. Ibbi-Sin
    Ibbi-Sin was the last king of the Third Dynasty of Ur, under whose troubled reign the Sumerian empire collapsed around the end of the 3rd millennium BCE.
  • C. Naram-Sin of Akkad
    Naram-Sin of Akkad was a powerful Mesopotamian king of the Akkadian Empire, famed for declaring himself a god and expanding the empire to its greatest territorial extent.
  • D. Amar-Sin
    Amar-Sin was a king of the Third Dynasty of Ur in ancient Mesopotamia, known for his extensive building projects and efforts to consolidate and expand his empire.
  • E. Sumu-la-El
    Sumu-la-El was an early Amorite king of Babylon known for consolidating and expanding the city-state into a significant regional power.
  • 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_69c008cdf2ac8190bb640c94478fb4ed completed March 22, 2026, 3:20 p.m.
NER Named-entity recognition batch_69c0643ac2b48190b2db036ce709e7ea completed March 22, 2026, 9:50 p.m.
NED1 Entity disambiguation (via context triple) batch_69c640a7ef8881909b00ce1f479f0fb4 completed March 27, 2026, 8:32 a.m.
Created at: March 22, 2026, 4:27 p.m.