Triple

T19018294
Position Surface form Disambiguated ID Type / Status
Subject Mughal–Sikh conflicts E465414 entity
Predicate hasPart P35 FINISHED
Object Battle of Sunam NE NERFINISHED

How this triple was built (3 steps)

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.

NER Named-entity recognition gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Battle of Sunam | Statement: [Mughal–Sikh conflicts, hasPart, Battle of Sunam]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Battle of Sunam
Context triple: [Mughal–Sikh conflicts, hasPart, Battle of Sunam]
  • A. Battle of Jemgum
    The Battle of Jemgum was a 1568 engagement in the early Eighty Years' War in which Spanish forces under the Duke of Alba decisively defeated Dutch rebels led by Louis of Nassau near the village of Jemgum in present-day Germany.
  • B. Battle of Hwangsanbeol
    The Battle of Hwangsanbeol was a decisive 660 CE clash in the Korean Three Kingdoms period in which Silla forces, allied with Tang China, defeated Baekje and paved the way for Baekje’s collapse.
  • C. Battle of Chapakchur
    The Battle of Chapakchur was a 15th-century military engagement in which the Aq Qoyunlu tribal confederation secured a decisive victory that helped establish its dominance in eastern Anatolia and surrounding regions.
  • D. Battle of Onjong
    The Battle of Onjong was an early Korean War clash in October 1950 in which Chinese forces first engaged United Nations troops, marking the beginning of large-scale Chinese intervention in the conflict.
  • E. Battle of Sandepu
    The Battle of Sandepu was a major land engagement of the Russo-Japanese War (1904–1905) in Manchuria, where Japanese and Russian forces clashed in harsh winter conditions shortly before the decisive Battle of Mukden.
  • F. None of above. chosen
  • G. Unsure - the case is ambiguous/there is not enough information to decide.
NED2 Entity disambiguation (via description) gpt-5-mini-2025-08-07
Target entity: Battle of Sunam
Target entity description: The Battle of Sunam was a military engagement between Mughal forces and Sikh warriors during the broader Mughal–Sikh conflicts in early modern India.
  • A. Battle of Jemgum
    The Battle of Jemgum was a 1568 engagement in the early Eighty Years' War in which Spanish forces under the Duke of Alba decisively defeated Dutch rebels led by Louis of Nassau near the village of Jemgum in present-day Germany.
  • B. Battle of Hwangsanbeol
    The Battle of Hwangsanbeol was a decisive 660 CE clash in the Korean Three Kingdoms period in which Silla forces, allied with Tang China, defeated Baekje and paved the way for Baekje’s collapse.
  • C. Battle of Chapakchur
    The Battle of Chapakchur was a 15th-century military engagement in which the Aq Qoyunlu tribal confederation secured a decisive victory that helped establish its dominance in eastern Anatolia and surrounding regions.
  • D. Battle of Onjong
    The Battle of Onjong was an early Korean War clash in October 1950 in which Chinese forces first engaged United Nations troops, marking the beginning of large-scale Chinese intervention in the conflict.
  • E. Battle of Sandepu
    The Battle of Sandepu was a major land engagement of the Russo-Japanese War (1904–1905) in Manchuria, where Japanese and Russian forces clashed in harsh winter conditions shortly before the decisive Battle of Mukden.
  • F. None of above. chosen

Provenance (2 batches)

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_69d8dd025c188190a1d81f5b4ec7e2c6 completed April 10, 2026, 11:20 a.m.
NER Named-entity recognition batch_69e5d6dd0e6c8190a6dc6af1f7901299 completed April 20, 2026, 7:33 a.m.
Created at: April 10, 2026, 12:02 p.m.