Triple
T29058330
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Athenaeus (son of Attalus I) |
E735454
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Pergamene royal family member |
C54657
|
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: Pergamene royal family member Context triple: [Athenaeus (son of Attalus I), instanceOf, Pergamene royal family 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.
Bithynian royal consort
A Bithynian royal consort is the spouse or recognized partner of a reigning king of Bithynia, holding a prominent position within the Hellenistic court and dynastic structure of the ancient Bithynian kingdom.
-
C.
member of the Heraclian dynasty
A member of the Heraclian dynasty is an individual belonging to the Byzantine imperial family that ruled from Emperor Heraclius’s accession in 610 to the death of Justinian II in 711, linked by blood or marriage to this ruling house.
-
D.
Seleucid princess
A Seleucid princess is a royal woman of the Hellenistic Seleucid dynasty, often used as a political pawn through strategic marriages to secure alliances and legitimize territorial control.
-
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.