Triple
T3520440
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Philip II of Macedon |
E74408
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Argead dynasty member |
C4182
|
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: Argead dynasty member Context triple: [Philip II of Macedon, instanceOf, Argead dynasty member]
-
A.
Macedonian king
chosen
A Macedonian king is a sovereign ruler of the ancient kingdom of Macedonia, wielding military, political, and religious authority over its territories and people.
-
B.
Herodian dynasty member
A Herodian dynasty member is an individual belonging to the ruling family established by Herod the Great, which governed Judea and surrounding regions under Roman authority during the late first century BCE and early first century CE.
-
C.
member of the Constantinian dynasty
A member of the Constantinian dynasty is an individual belonging to the imperial family that ruled the Roman Empire from the rise of Constantine the Great in the early 4th century until the death of his descendants later that century.
-
D.
Capetian dynasty member
A Capetian dynasty member is an individual belonging by blood or legitimate descent to the royal house founded by Hugh Capet, which ruled France and various European realms from the late 10th century onward.
-
E.
Carolingian dynasty member
A Carolingian dynasty member is an individual belonging to the Frankish royal family that ruled large parts of Western and Central Europe from the 8th to 10th centuries, originating with Charles Martel and reaching its height under Charlemagne.
- 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_69ad85d0c5488190a3d8e02ebd01a1aa |
completed | March 8, 2026, 2:21 p.m. |
Created at: March 8, 2026, 3:19 p.m.