Triple
T21641306
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | War with Moab |
E534093
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | biblical war |
C34219
|
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: biblical war Context triple: [War with Moab, instanceOf, biblical war]
-
A.
biblical military force
A biblical military force is an organized group of warriors, often divinely sanctioned or opposed, that engages in battles central to the narrative and theological themes of Scripture.
-
B.
ancient Near Eastern war
chosen
Ancient Near Eastern war encompasses the organized, often ritualized conflicts between early civilizations of Mesopotamia, Egypt, Anatolia, and the Levant, characterized by chariot warfare, fortified cities, imperial expansion, and the intertwining of military action with religion and kingship.
-
C.
biblical epic
A biblical epic is a grand, large-scale film or narrative that dramatizes stories, characters, and events from the Bible with sweeping visuals, heightened emotion, and moral or spiritual themes.
-
D.
Crusades battle
A Crusades battle is a large-scale medieval military engagement between Christian and Muslim forces (and their allies) fought primarily in the Eastern Mediterranean and surrounding regions as part of the religiously motivated campaigns known as the Crusades.
-
E.
biblical kingdom
A biblical kingdom is a divinely oriented realm or nation, often ruled by a monarch, whose identity, laws, and destiny are framed and interpreted through the narratives, covenants, and theological themes of the Bible.
- 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_69e0c465ae7481908577b7209fdb2a77 |
completed | April 16, 2026, 11:13 a.m. |
Created at: April 16, 2026, 6:35 p.m.