Triple
T38417804
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sohaemus of Armenia |
E903144
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | member of the Roman client royalty |
C54925
|
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 Roman client royalty Context triple: [Sohaemus of Armenia, instanceOf, member of the Roman client royalty]
-
A.
member of a client royal family
chosen
A member of a client royal family is an individual belonging by birth or marriage to a subordinate monarchy that maintains its own dynastic status and limited authority under the protection or suzerainty of a more powerful sovereign state.
-
B.
member of the Roman nobility
A member of the Roman nobility is an individual belonging to the elite social class of ancient Rome, distinguished by hereditary status, political influence, and privileged legal and economic rights.
-
C.
member of the Roman imperial family
A member of the Roman imperial family is an individual related by blood, marriage, or adoption to the reigning emperor, often holding elevated social status, political influence, and potential claims to succession within the Roman Empire.
-
D.
member of a former royal family
A member of a former royal family is an individual descended from or previously holding status within a monarchy that has since lost its ruling power or official political authority.
-
E.
member of a royal family
A member of a royal family is an individual related by blood, marriage, or adoption to a reigning or formerly reigning monarch, typically holding a recognized title, status, or role within the monarchy.
- 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.