Triple
T4119708
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Justinianic reconquests |
E90381
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Byzantine military campaign |
C11928
|
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: Byzantine military campaign Context triple: [Justinianic reconquests, instanceOf, Byzantine military campaign]
-
A.
Roman military campaign
chosen
A Roman military campaign is a coordinated series of operations conducted by Roman forces, combining strategic planning, logistics, and battlefield tactics to achieve political, territorial, or defensive objectives.
-
B.
papal military campaign
A papal military campaign is an organized armed expedition initiated, sanctioned, or led by the pope or the Papal States to pursue religious, political, or territorial objectives.
-
C.
Byzantine–Vandal War
The Byzantine–Vandal War (533–534) was a military campaign in which the Eastern Roman (Byzantine) Empire under Emperor Justinian I defeated the Vandal Kingdom in North Africa, restoring imperial control over the region.
-
D.
Mughal campaign
A Mughal campaign is a military expedition undertaken by the Mughal Empire to expand, consolidate, or defend its territories through organized warfare and strategic operations.
-
E.
Mongol invasion of Europe battle
A Mongol invasion of Europe battle is a military engagement in which Mongol forces confront European armies during their 13th-century westward campaigns, characterized by highly mobile cavalry tactics, psychological warfare, and often decisive Mongol victories.
- 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_69aed95c080881908125e30c5dcdc6f8 |
completed | March 9, 2026, 2:29 p.m. |
Created at: March 9, 2026, 3:41 p.m.