Triple
T18622410
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Herod (son of Cleopatra of Jerusalem) |
E455187
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Herodian dynasty prince |
C4224
|
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: Herodian dynasty prince Context triple: [Herod (son of Cleopatra of Jerusalem), instanceOf, Herodian dynasty prince]
-
A.
Herodian dynasty member
chosen
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.
Herodian king
A Herodian king is a ruler from the Herodian dynasty who governed parts of Judea and surrounding regions under Roman authority during the late first century BCE and early first century CE.
-
C.
Herodian princess
A Herodian princess is a royal woman belonging to the Herodian dynasty that ruled Judea and surrounding regions under Roman influence, often serving as a political link between Jewish, Roman, and neighboring royal courts.
-
D.
Nabatean prince
A Nabatean prince is a royal male member of the ancient Nabatean kingdom’s ruling family, typically involved in governance, diplomacy, and the management of trade and territorial affairs.
-
E.
Palmyrene prince
A Palmyrene prince is a male member of the royal or ruling elite of the ancient city-state of Palmyra in Roman Syria, often involved in governance, military leadership, and regional diplomacy.
- 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_69d8d38cc7948190a55ea64e5638994e |
completed | April 10, 2026, 10:40 a.m. |
Created at: April 10, 2026, 11:46 a.m.