Triple

T15314362
Position Surface form Disambiguated ID Type / Status
Subject Drypetis E366116 entity
Predicate instanceOf P0 FINISHED
Object member of the Achaemenid dynasty C13304 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: member of the Achaemenid dynasty
Context triple: [Drypetis, instanceOf, member of the Achaemenid dynasty]
  • A. member of the Pahlavi dynasty
    A member of the Pahlavi dynasty is an individual belonging by blood or marriage to the Iranian royal family that ruled Iran from 1925 until the 1979 Islamic Revolution.
  • B. Achaemenid noble chosen
    An Achaemenid noble is a high-ranking member of the Persian aristocracy who held land, military command, and administrative authority under the Achaemenid Empire, often serving as a close supporter and regional representative of the Great King.
  • C. 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.
  • D. member of the Battiad dynasty
    A member of the Battiad dynasty is an individual belonging to the royal lineage that ruled the ancient Greek city-state of Cyrene in North Africa, traditionally founded by Battus I and his descendants.
  • E. member of the Magonid dynasty
    A member of the Magonid dynasty is an individual belonging to the powerful Carthaginian ruling family, active mainly in the 6th–4th centuries BCE, known for producing influential military and political leaders who shaped Carthage’s expansion and foreign policy.
  • 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_69d85a113ee881908e297a1d38dd79fa completed April 10, 2026, 2:01 a.m.
Created at: April 10, 2026, 3:16 a.m.