Triple

T30884325
Position Surface form Disambiguated ID Type / Status
Subject Battle of Shaykan E786716 entity
Predicate primaryTacticMahdists P75814 FINISHED
Object encirclement and surprise attacks LITERAL FINISHED

How this triple was built (2 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: encirclement and surprise attacks | Statement: [Battle of Shaykan, primaryTacticMahdists, encirclement and surprise attacks]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: primaryTacticMahdists
Context triple: [Battle of Shaykan, primaryTacticMahdists, encirclement and surprise attacks]
  • A. combatantStrengthMahdists
    Indicates the level or measure of military strength or fighting capability possessed by the Mahdist combatant forces.
  • B. primaryTacticOttomans
    Indicates the main military or strategic method predominantly employed by the Ottoman forces in a given conflict or context.
  • C. hasPrimaryTactic chosen
    Indicates that an entity is associated with its main or most commonly used tactic or method of operation.
  • D. strategyUsedByRashidun
    Indicates that a particular strategy was employed or implemented by the Rashidun.
  • E. primaryTacticConfederate
    Indicates that the primary tactic or strategy employed involves or is characterized by the actions or role of a Confederate entity.
  • F. None of above.

Provenance (3 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_69f224bbfa7c81908448e0c261c523e3 completed April 29, 2026, 3:33 p.m.
NER Named-entity recognition batch_6a03460f3a8c8190ae3f4cd69e0e54d9 completed May 12, 2026, 3:23 p.m.
PD Predicate disambiguation batch_6a0345810b3481908aec06ab2b712e12 completed May 12, 2026, 3:21 p.m.
Created at: April 29, 2026, 8:48 p.m.