Triple
T651021
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Assyrian conquest of the Kingdom of Israel |
E11345
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Assyrian military campaign |
C340
|
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 military campaign Context triple: [Assyrian conquest of the Kingdom of Israel, instanceOf, Assyrian military campaign]
-
A.
military campaign phase
A military campaign phase is a distinct, time-bounded segment of a broader military operation characterized by specific objectives, actions, and resource allocations that contribute to the overall strategic goal.
-
B.
imperial war
Imperial war is a large-scale, often expansionist conflict waged by an empire to acquire, control, or maintain dominance over territories, peoples, or resources beyond its original borders.
-
C.
military campaign theater
A military campaign theater is a geographically defined area where coordinated military operations and strategies are conducted to achieve specific objectives within a broader conflict.
-
D.
military operation
chosen
A military operation is a coordinated and planned set of actions conducted by armed forces to achieve specific strategic, operational, or tactical objectives.
-
E.
ancient Greek war
Ancient Greek war encompasses the organized, often city-state-driven conflicts of classical Greece, characterized by hoplite phalanxes, naval battles like those at Salamis, shifting alliances, and a fusion of military, political, and cultural motives.
- 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_69a493266a2881909daf4c40f719dee8 |
completed | March 1, 2026, 7:27 p.m. |
Created at: March 1, 2026, 7:36 p.m.