Triple
T19081622
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Omride dynasty |
E467045
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ancient Israelite dynasty |
C36619
|
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: ancient Israelite dynasty Context triple: [Omride dynasty, instanceOf, ancient Israelite dynasty]
-
A.
Amorite dynasty
The Amorite dynasty refers to the line of rulers of Amorite origin who established and governed powerful city-states and kingdoms in ancient Mesopotamia, most notably the First Babylonian Dynasty under Hammurabi.
-
B.
ancient Near Eastern dynasty
chosen
An ancient Near Eastern dynasty is a succession of rulers from the same family or lineage that governed a state or empire in the Near East during antiquity, shaping its political, cultural, and religious development over time.
-
C.
rabbinic dynasty
A rabbinic dynasty is a multigenerational family lineage in which religious authority, leadership, and scholarly roles are passed down among rabbis, often shaping the spiritual life and traditions of a particular Jewish community or movement.
-
D.
Sumerian dynasty
A Sumerian dynasty is a succession of rulers from the same family or lineage who governed a Sumerian city-state or region in ancient Mesopotamia.
-
E.
ancient Greek dynasty
An ancient Greek dynasty is a succession of rulers from the same family or lineage who governed a Greek city-state, kingdom, or region over multiple generations in antiquity.
- 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_69d8dd04f4488190b1121cc53ef2bfd6 |
completed | April 10, 2026, 11:20 a.m. |
Created at: April 10, 2026, 12:04 p.m.