Triple

T12319405
Position Surface form Disambiguated ID Type / Status
Subject Mytilenean revolt E293687 entity
Predicate instanceOf P0 FINISHED
Object event in the Peloponnesian War C4369 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: event in the Peloponnesian War
Context triple: [Mytilenean revolt, instanceOf, event in the Peloponnesian War]
  • A. 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.
  • B. ancient Greek war chosen
    Ancient Greek war encompasses the organized, often city-state-driven conflicts of classical Greece, characterized by hoplite phalanxes, naval battles like those at Salamis, shifting alliances, and a fusion of military, political, and cultural motives.
  • C. battle of the First Punic War
    A battle of the First Punic War is a specific military engagement fought between Rome and Carthage (and their allies) between 264 and 241 BCE, characterized by evolving naval and land tactics that shaped the course of Mediterranean power.
  • D. event in the Greek War of Independence
    An event in the Greek War of Independence is a significant historical occurrence between 1821 and 1830 that influenced the course, outcome, or broader context of the Greek struggle to gain independence from the Ottoman Empire.
  • E. event in the Crimean War
    An event in the Crimean War is a specific historical occurrence—such as a battle, diplomatic action, military maneuver, or political decision—that took place between 1853 and 1856 and contributed to the course and outcome of the conflict.
  • 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_69d6ab6ae0dc8190b1522a9c1c55c114 completed April 8, 2026, 7:24 p.m.
Created at: April 8, 2026, 9:53 p.m.