Triple

T6944117
Position Surface form Disambiguated ID Type / Status
Subject Twenty-seventh Dynasty of Egypt E160751 entity
Predicate instanceOf P0 FINISHED
Object Achaemenid Egyptian dynasty C15295 CONCEPT FINISHED

How this triple was built (1 step)

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.

CD Concept disambiguation gpt-5-mini-2025-08-07
Target class: Achaemenid Egyptian dynasty
Context triple: [Twenty-seventh Dynasty of Egypt, instanceOf, Achaemenid Egyptian dynasty]
  • A. ancient Greek dynasty
    An ancient Greek dynasty is a succession of rulers from the same family or lineage who governed a Greek city-state, kingdom, or region over multiple generations in antiquity.
  • B. Iranian legendary dynasty
    An Iranian legendary dynasty is a mytho-historical royal lineage in Iranian tradition, often featured in epic literature like the Shahnameh, that symbolizes ideal kingship, cultural values, and the cosmic struggle between good and evil.
  • C. Persianate dynasty chosen
    A Persianate dynasty is a ruling family or political regime that, regardless of its ethnic origin, adopts and promotes Persian language, culture, administrative practices, and aesthetic ideals as the core framework of its governance and elite identity.
  • D. Ancient Egyptian dynasty
    An Ancient Egyptian dynasty is a succession of rulers from the same family or lineage who governed Egypt during a distinct historical period, often characterized by shared political, cultural, and religious developments.
  • E. Achaemenid ruler
    An Achaemenid ruler is a monarch of the ancient Persian Achaemenid Empire who exercised centralized authority over a vast, multicultural territory through a system of satrapies, royal roads, and imperial administration.
  • F. None of above.

Provenance (1 batch)

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_69c6884f3db4819080ad65da69386206 completed March 27, 2026, 1:38 p.m.
Created at: March 27, 2026, 2:28 p.m.