Triple

T31135215
Position Surface form Disambiguated ID Type / Status
Subject Treaties of the Vandal Kingdom E793619 entity
Predicate instanceOf P0 FINISHED
Object Roman–barbarian treaty C60390 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: Roman–barbarian treaty
Context triple: [Treaties of the Vandal Kingdom, instanceOf, Roman–barbarian treaty]
  • A. Byzantine–Sasanian treaty
    A Byzantine–Sasanian treaty is a formal diplomatic agreement concluded between the Eastern Roman (Byzantine) Empire and the Sasanian (Sassanid) Persian Empire, typically defining terms of peace, territorial boundaries, tribute, and mutual obligations.
  • B. battle of the Lazic War
    A battle of the Lazic War is a military engagement between Byzantine and Sasanian (and allied) forces in the Lazica region, fought to control strategic Black Sea access and regional influence during the 6th century.
  • C. Frankish–Visigothic conflict
    The Frankish–Visigothic conflict refers to the series of military, political, and territorial struggles between the Frankish and Visigothic kingdoms in late antiquity and the early Middle Ages, particularly over control of Gaul and Hispania.
  • D. Roman–Parthian war
    The Roman–Parthian war is a conceptual class representing the series of military conflicts and political struggles between the Roman Empire and the Parthian Empire over control of territories in the Near East from the 1st century BCE to the 3rd century CE.
  • E. Roman–Dacian war
    The Roman–Dacian war refers to the series of military conflicts between the Roman Empire and the Dacian Kingdom in the late 1st and early 2nd centuries AD, culminating in Rome’s conquest and annexation of Dacia under Emperor Trajan.
  • 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_69f224d2b3a48190aa9dd26fbf6eab1a completed April 29, 2026, 3:33 p.m.
Created at: April 29, 2026, 9:05 p.m.