Triple
T15802610
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fall of Samaria |
E383132
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Assyrian conquest |
C36516
|
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: Assyrian conquest Context triple: [Fall of Samaria, instanceOf, Assyrian conquest]
-
A.
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.
-
B.
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.
-
C.
Neo-Babylonian dynasty
The Neo-Babylonian dynasty was the ruling line of kings (626–539 BCE) that restored Babylon’s power in Mesopotamia, overseeing a cultural and architectural renaissance before falling to the Persian Empire.
-
D.
Byzantine–Sasanian war
The Byzantine–Sasanian war is a prolonged series of military conflicts between the Eastern Roman (Byzantine) Empire and the Sasanian Persian Empire, marked by shifting frontiers, religious and political rivalry, and significant impacts on the balance of power in the Late Antique Near East.
-
E.
Greek–Persian conflict
The Greek–Persian conflict is a historical class representing the prolonged series of political, military, and cultural confrontations between the Greek city-states and the Persian Empire, encompassing causes, key battles, strategies, and outcomes that shaped classical antiquity.
- 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_69d86da16e188190b89af699f1ed0bfe |
completed | April 10, 2026, 3:25 a.m. |
Created at: April 10, 2026, 4:48 a.m.