Triple
T16681325
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Assyrian siege of Jerusalem (701 BCE) |
E405345
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | event in the history of ancient Israel and Judah |
C13438
|
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: event in the history of ancient Israel and Judah Context triple: [Assyrian siege of Jerusalem (701 BCE), instanceOf, event in the history of ancient Israel and Judah]
-
A.
event in the Hebrew Bible
An event in the Hebrew Bible is a narrated occurrence—historical, theological, or symbolic—in which God’s purposes unfold through actions, experiences, or interventions in the lives of individuals or communities.
-
B.
Old Testament event
An Old Testament event is a significant occurrence or narrative described in the Hebrew Bible that shapes the religious, historical, and theological context of ancient Israel.
-
C.
region of ancient Palestine
A region of ancient Palestine is a geographically and culturally distinct area within the historical land of Palestine, defined by its political boundaries, settlements, and role in biblical and Near Eastern history.
-
D.
era in Jewish history
An era in Jewish history is a distinct period marked by characteristic religious, cultural, political, and social developments that shape the trajectory and identity of the Jewish people.
-
E.
event in ancient history
chosen
An event in ancient history is a significant occurrence or series of actions that took place in early human civilizations and has had a lasting impact on cultural, political, or social development.
- 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_69d8838c28748190b3f5967c743940ab |
completed | April 10, 2026, 4:58 a.m. |
Created at: April 10, 2026, 5:19 a.m.