Triple

T13817624
Position Surface form Disambiguated ID Type / Status
Subject Neo-Babylonian–Kingdom of Judah wars E332058 entity
Predicate instanceOf P0 FINISHED
Object ancient Near Eastern war C34219 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: ancient Near Eastern war
Context triple: [Neo-Babylonian–Kingdom of Judah wars, instanceOf, ancient Near Eastern war]
  • A. Bronze Age battle
    A Bronze Age battle is an armed conflict between organized groups during the Bronze Age, typically involving bronze weapons, chariots, early fortifications, and tactics shaped by emerging complex societies.
  • B. ancient Greek war
    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. ancient Near Eastern war song
    An ancient Near Eastern war song is a ritualized poetic chant or hymn that invokes deities, recounts heroic battles, and seeks divine favor or intimidation of enemies in the context of warfare.
  • D. war in the Middle Ages
    War in the Middle Ages encompasses the organized, often feudal-based conflicts fought between kingdoms, nobles, and religious powers using evolving military technologies, tactics, and social structures from roughly the 5th to the 15th century.
  • E. Greek–Persian conflict
    The Greek–Persian conflict is a historical class representing the prolonged series of political, military, and cultural confrontations between the Greek city-states and the Persian Empire, encompassing causes, key battles, strategies, and outcomes that shaped classical antiquity.
  • F. None of above. chosen

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_69d81c59f8808190a851bc56afdc55e9 completed April 9, 2026, 9:38 p.m.
Created at: April 9, 2026, 10:12 p.m.