Triple
T3272417
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mandane of Media |
E68679
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Achaemenid dynasty figure |
C4222
|
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 dynasty figure Context triple: [Mandane of Media, instanceOf, Achaemenid dynasty figure]
-
A.
Achaemenid ruler
chosen
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.
-
B.
Achaemenid inscription
An Achaemenid inscription is a formal text carved or written on durable materials during the Achaemenid Empire, typically in multiple languages and scripts, to record royal proclamations, commemorations, or religious dedications.
-
C.
Byzantine imperial dynasty
A Byzantine imperial dynasty is a succession of related rulers who governed the Eastern Roman (Byzantine) Empire, shaping its political, religious, and cultural life over multiple generations.
-
D.
Herodian dynasty member
A Herodian dynasty member is an individual belonging to the ruling family established by Herod the Great, which governed Judea and surrounding regions under Roman authority during the late first century BCE and early first century CE.
-
E.
Neo-Babylonian king
A Neo-Babylonian king is the sovereign ruler of the Neo-Babylonian Empire (c. 626–539 BCE), responsible for military leadership, monumental building projects, religious patronage, and the administration of law and tribute across Mesopotamia.
- 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_69ad859b54f881909bf530d549caf2fd |
completed | March 8, 2026, 2:20 p.m. |
Created at: March 8, 2026, 3:10 p.m.