Triple
T29058329
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Athenaeus (son of Attalus I) |
E735454
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Attalid dynasty member |
C54656
|
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: Attalid dynasty member Context triple: [Athenaeus (son of Attalus I), instanceOf, Attalid dynasty member]
-
A.
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.
-
B.
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.
-
C.
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.
-
D.
member of the Argead dynasty
A member of the Argead dynasty is an individual belonging to the ancient Macedonian royal house that ruled Macedon, including figures such as Philip II and Alexander the Great.
-
E.
member of the Antipatrid dynasty
A member of the Antipatrid dynasty is an individual belonging to the Macedonian royal house founded by Antipater, which briefly ruled Macedonia in the late 4th century BCE following the fragmentation of Alexander the Great’s empire.
- 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_69f077e85498819088b65186550da8cd |
completed | April 28, 2026, 9:03 a.m. |
Created at: April 28, 2026, 10:13 a.m.