Triple
T34650948
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Helenus (son of Pyrrhus) |
E889836
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | member of Epirote royal family |
C61937
|
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 Epirote royal family Context triple: [Helenus (son of Pyrrhus), instanceOf, member of Epirote royal family]
-
A.
Pergamene royal family member
A Pergamene royal family member is an individual belonging to the ruling dynasty of the Hellenistic Kingdom of Pergamon, holding hereditary status, political influence, and often religious or cultural authority within the realm.
-
B.
Attalid dynasty member
An Attalid dynasty member is an individual belonging to the Hellenistic royal family that ruled the kingdom of Pergamon in Asia Minor from the early 3rd to the mid-2nd century BCE.
-
C.
Spartocid dynasty member
A Spartocid dynasty member is an individual belonging to the ruling family of the Bosporan Kingdom, which governed the Cimmerian Bosporus region from the 5th to the 2nd century BCE.
-
D.
member of the Antigonid dynasty
A member of the Antigonid dynasty is an individual belonging to the Hellenistic royal family that ruled Macedonia and parts of Greece from the late 4th to the 2nd century BCE, descending from Antigonus I Monophthalmus.
-
E.
Ascanian dynasty member
An Ascanian dynasty member is an individual belonging to the medieval and early modern German noble house of Ascania, which ruled various principalities such as Anhalt, Brandenburg, and Saxony.
- 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_69f349d825c88190bfc6170ac9281260 |
completed | April 30, 2026, 12:23 p.m. |
Created at: May 1, 2026, 2:04 a.m.