Triple

T14410517
Position Surface form Disambiguated ID Type / Status
Subject Gundobad E357310 entity
Predicate instanceOf P0 FINISHED
Object late Roman general C10598 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: late Roman general
Context triple: [Gundobad, instanceOf, late Roman general]
  • A. Roman military commander chosen
    A Roman military commander is a high-ranking officer responsible for leading legions, planning and executing campaigns, maintaining discipline, and securing Rome’s political and territorial interests through organized warfare.
  • B. late Roman provincial governor
    A late Roman provincial governor was an imperial official responsible for administering a province’s civil government, justice, taxation, and local defense under the increasingly centralized and bureaucratic structures of the later Roman Empire.
  • C. Roman soldier
    A Roman soldier is a disciplined, heavily trained infantryman of ancient Rome’s military, equipped with standardized armor and weapons, who served to expand and protect the Roman state.
  • D. Roman consul
    A Roman consul was one of the two annually elected chief magistrates of the Roman Republic (and later an important office in the Empire), holding supreme civil and military authority and presiding over the Senate and assemblies.
  • E. Gallic emperor
    A Gallic emperor is a ruler who claimed imperial authority over the breakaway Gallic Empire (comprising parts of Roman Gaul, Britain, and sometimes Spain) during the 3rd-century Crisis of the Roman 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_69d82793421c8190861eb0e673b085de completed April 9, 2026, 10:26 p.m.
Created at: April 10, 2026, 1:17 a.m.