Triple
T18758734
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Orontid dynasty |
E458715
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ancient Armenian dynasty |
C34459
|
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: ancient Armenian dynasty Context triple: [Orontid dynasty, instanceOf, ancient Armenian dynasty]
-
A.
Armenian dynasty
chosen
An Armenian dynasty is a hereditary ruling family originating from Armenia that held political power and authority over Armenian territories during a specific historical period.
-
B.
Assyrian dynasty
An Assyrian dynasty is a ruling lineage or succession of kings that governed the Assyrian state or empire during a distinct historical period in ancient Mesopotamia.
-
C.
medieval Armenian kingdom
A medieval Armenian kingdom is a historically situated political entity in the Armenian Highlands, characterized by Armenian dynastic rule, Christian cultural identity, and feudal socio-political structures interacting with neighboring empires.
-
D.
ancient Iranian dynasty
An ancient Iranian dynasty is a long-ruling hereditary line of monarchs originating in the Iranian cultural sphere that governed significant territories in antiquity, shaping the region’s political, social, and religious history.
-
E.
Cappadocian dynasty
The Cappadocian dynasty was a line of Byzantine emperors of Cappadocian origin, notably including Basil I and his successors, who ruled the Byzantine Empire from the late 9th to the early 11th centuries.
- 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_69d8d395dba0819087568404508590cb |
completed | April 10, 2026, 10:40 a.m. |
Created at: April 10, 2026, 11:52 a.m.