Triple
T20655529
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John Gaddi |
E507615
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Hasmonean family member |
C11401
|
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: Hasmonean family member Context triple: [John Gaddi, instanceOf, Hasmonean family member]
-
A.
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.
-
B.
Hasmoneans
chosen
The Hasmoneans were a Jewish priestly dynasty that led the Maccabean revolt against Seleucid rule and subsequently governed an independent Judean kingdom in the 2nd–1st centuries BCE.
-
C.
Levitical family
A Levitical family is a household descended from the biblical tribe of Levi, traditionally dedicated to priestly and temple-related duties within ancient Israelite religious life.
-
D.
member of the Magonid dynasty
A member of the Magonid dynasty is an individual belonging to the powerful Carthaginian ruling family, active mainly in the 6th–4th centuries BCE, known for producing influential military and political leaders who shaped Carthage’s expansion and foreign policy.
-
E.
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.
- 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_69e0b4bf58c081908e52a4500e03ff83 |
completed | April 16, 2026, 10:06 a.m. |
Created at: April 16, 2026, 11:43 a.m.