Triple

T9371088
Position Surface form Disambiguated ID Type / Status
Subject Marcus Claudius Marcellus E225530 entity
Predicate instanceOf P0 FINISHED
Object military commander in the Second Punic War 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: military commander in the Second Punic War
Context triple: [Marcus Claudius Marcellus, instanceOf, military commander in the Second Punic War]
  • A. Carthaginian military commander
    A Carthaginian military commander is a high-ranking officer from ancient Carthage responsible for planning and leading land or naval forces in campaigns, battles, and strategic defense of Carthaginian interests.
  • B. event in the Second Punic War
    An "event in the Second Punic War" represents a historically significant occurrence—such as a battle, treaty, political decision, or strategic maneuver—that took place between 218 and 201 BCE and influenced the course or outcome of the conflict between Rome and Carthage.
  • C. Samnite commander
    A Samnite commander is a high-ranking military leader from the ancient Samnite tribes of central and southern Italy, responsible for organizing warriors, planning tactics, and leading them in battle against rival states such as Rome.
  • D. 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.
  • E. Athenian general
    An Athenian general is a high-ranking military and political leader of ancient Athens responsible for commanding armies, planning campaigns, and often influencing civic decision-making.
  • 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_69ca842cbddc819099d71ecec48cf9e5 completed March 30, 2026, 2:09 p.m.
Created at: March 30, 2026, 7:43 p.m.