Triple
T36658886
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mithridates V of Parthia |
E905066
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | member of the Arsacid dynasty |
C65878
|
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 Arsacid dynasty Context triple: [Mithridates V of Parthia, instanceOf, member of the Arsacid dynasty]
-
A.
member of the Arsacid dynasty of Armenia
A member of the Arsacid dynasty of Armenia is an individual belonging to the royal house that ruled the Armenian kingdom from the 1st to the 5th century CE, often serving as king or high-ranking noble within its hereditary monarchical structure.
-
B.
Member of the Orontid dynasty
A Member of the Orontid dynasty is an individual belonging to the ancient Armenian royal house that ruled parts of Armenia and neighboring regions from the Achaemenid through the Hellenistic periods.
-
C.
Ezzonid dynasty member
An Ezzonid dynasty member is an individual belonging to the influential noble family that held significant territorial and political power in the Rhineland region of the Holy Roman Empire during the 10th and 11th centuries.
-
D.
member of the Germiyanid dynasty
A member of the Germiyanid dynasty is an individual belonging to the medieval Anatolian Turkish ruling family that governed the Beylik of Germiyan from the late 13th to the early 15th century.
-
E.
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.
- F. None of above. chosen
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_69f76e6e3b908190970251b30f76ad71 |
completed | May 3, 2026, 3:49 p.m. |
Created at: May 3, 2026, 4:11 p.m.