Triple

T32242554
Position Surface form Disambiguated ID Type / Status
Subject Reunification of the Roman Empire under Aurelian E823656 entity
Predicate instanceOf P0 FINISHED
Object Roman imperial 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: Roman imperial campaign
Context triple: [Reunification of the Roman Empire under Aurelian, instanceOf, Roman imperial 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. Roman battle
    A Roman battle is a large-scale military engagement in which Roman forces, often organized into legions and auxiliaries, confront enemy armies using disciplined formations, tactical maneuvers, and a combination of infantry, cavalry, and siege weaponry.
  • C. 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.
  • 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 imperial policy
    Roman imperial policy refers to the strategies, laws, and administrative practices employed by Roman emperors to maintain control, integrate diverse provinces, manage resources, and project power across the empire.
  • 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_69f3490cdda88190a9d61e11252a771f completed April 30, 2026, 12:20 p.m.
Created at: May 1, 2026, 12:40 a.m.