Triple
T38417803
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sohaemus of Armenia |
E903144
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | 2nd-century monarch |
C41449
|
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: 2nd-century monarch Context triple: [Sohaemus of Armenia, instanceOf, 2nd-century monarch]
-
A.
2nd-century ruler
chosen
A 2nd-century ruler is a sovereign or governing authority who held political power and exercised control over a state or territory during the years 100–199 CE.
-
B.
3rd-century ruler
A 3rd-century ruler is a sovereign or governing authority who held power during the years 200–299 CE, navigating the political, military, and social upheavals characteristic of that era.
-
C.
Herodian king
A Herodian king is a ruler from the Herodian dynasty who governed parts of Judea and surrounding regions under Roman authority during the late first century BCE and early first century CE.
-
D.
3rd-century Roman emperor
A 3rd-century Roman emperor is the sovereign ruler of the Roman Empire during the 200s CE, navigating intense military, political, and economic crises while asserting imperial authority over a vast and often unstable realm.
-
E.
2nd-century BCE ruler
A 2nd-century BCE ruler is a sovereign who governed a state or empire between 200 and 101 BCE, navigating the complex political, military, and cultural dynamics of the Hellenistic, Roman Republican, and other contemporaneous civilizations.
- 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_69f76e67e4fc8190a7d08dfe9a8af998 |
completed | May 3, 2026, 3:48 p.m. |
Created at: May 3, 2026, 4:31 p.m.