Triple
T4012568
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alexander |
E90679
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Hasmonean dynasty 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 dynasty member Context triple: [Alexander, instanceOf, Hasmonean dynasty 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.
Judean official
A Judean official is a governmental or administrative authority from ancient Judea responsible for overseeing civic, legal, or religious affairs within the region.
-
D.
Isaurian dynasty ruler
An Isaurian dynasty ruler is a Byzantine emperor from the 8th–9th century Isaurian line who governed the Eastern Roman Empire and is often associated with initiating and enforcing the policy of iconoclasm.
-
E.
member of the Flavian dynasty
A member of the Flavian dynasty is an individual belonging to the Roman imperial family that ruled the Roman Empire from 69 to 96 CE, including emperors Vespasian, Titus, and Domitian and their close relatives.
- 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_69aed95e44088190aff7d90a151b1b20 |
completed | March 9, 2026, 2:29 p.m. |
Created at: March 9, 2026, 3:34 p.m.