Triple
T16681326
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Assyrian siege of Jerusalem (701 BCE) |
E405345
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | event in the Neo-Assyrian Empire |
C38232
|
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 Neo-Assyrian Empire Context triple: [Assyrian siege of Jerusalem (701 BCE), instanceOf, event in the Neo-Assyrian Empire]
-
A.
Assyrian conquest
Assyrian conquest refers to the aggressive military expansion and subjugation of neighboring regions by the ancient Assyrian Empire, characterized by advanced warfare tactics, strategic deportations, and administrative control to build a powerful Near Eastern empire.
-
B.
Neo-Assyrian dynasty
The Neo-Assyrian dynasty was the ruling line of kings that governed the Neo-Assyrian Empire (c. 911–609 BCE), overseeing its expansion into the dominant military and political power of the ancient Near East.
-
C.
Assyrian dynasty
An Assyrian dynasty is a ruling lineage or succession of kings that governed the Assyrian state or empire during a distinct historical period in ancient Mesopotamia.
-
D.
Mesopotamian festival
A Mesopotamian festival is a recurring religious and civic celebration in ancient Mesopotamia that honored specific deities through rituals, processions, offerings, and communal feasting, reinforcing cosmic order and social cohesion.
-
E.
Neo-Assyrian king
A Neo-Assyrian king is the supreme monarch of the Neo-Assyrian Empire, wielding absolute political, military, and religious authority to expand and maintain imperial power across the ancient Near East.
- F. None of above. chosen
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.