Triple
T26653422
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of the Boarn |
E666429
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | early medieval battle |
C17502
|
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: early medieval battle Context triple: [Battle of the Boarn, instanceOf, early medieval battle]
-
A.
Bronze Age battle
A Bronze Age battle is an armed conflict between organized groups during the Bronze Age, typically involving bronze weapons, chariots, early fortifications, and tactics shaped by emerging complex societies.
-
B.
6th-century conflict
A 6th-century conflict is a historically documented war, battle, or prolonged military-political struggle that occurred between 500 and 599 CE, involving organized groups or states and significantly impacting the societies of that era.
-
C.
war in the Middle Ages
chosen
War in the Middle Ages encompasses the organized, often feudal-based conflicts fought between kingdoms, nobles, and religious powers using evolving military technologies, tactics, and social structures from roughly the 5th to the 15th century.
-
D.
7th-century conflict
A 7th-century conflict is a military or political struggle that occurred between 600 and 699 CE, typically involving early medieval states, empires, or tribes and shaped by the religious, cultural, and territorial dynamics of that era.
-
E.
Roman–Sasanian War engagement
A Roman–Sasanian War engagement is a specific military confrontation between Roman (or Eastern Roman/Byzantine) and Sasanian Persian forces within the broader series of Roman–Sasanian conflicts.
- 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_69ee9cf8c7188190b9b00270a8a89164 |
completed | April 26, 2026, 11:17 p.m. |
Created at: April 27, 2026, 2:34 a.m.