Triple

T14698611
Position Surface form Disambiguated ID Type / Status
Subject Roman conquest of Spain E345229 entity
Predicate instanceOf P0 FINISHED
Object Roman military expansion 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 military expansion
Context triple: [Roman conquest of Spain, instanceOf, Roman military expansion]
  • 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. Greek expansion
    Greek expansion refers to the historical process by which Greek culture, language, political influence, and settlements spread beyond the Greek mainland into the wider Mediterranean and Near Eastern regions through colonization, conquest, and trade.
  • C. 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.
  • D. Roman frontier
    The Roman frontier was the shifting boundary zone of the Roman Empire, marked by fortifications, military roads, and garrisoned settlements that controlled movement, trade, and defense between Roman territories and neighboring peoples.
  • E. Napoleonic expansion
    Napoleonic expansion refers to the rapid territorial and political growth of the French Empire under Napoleon Bonaparte, achieved through military conquest, strategic alliances, and administrative reforms across Europe in the early 19th century.
  • 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_69d822e4a8c08190a155df736bb7bc13 completed April 9, 2026, 10:06 p.m.
Created at: April 10, 2026, 1:28 a.m.