Triple

T18991434
Position Surface form Disambiguated ID Type / Status
Subject Battle of Gawilghur E464692 entity
Predicate commander P1061 FINISHED
Object Pohlmann NE NERFINISHED

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: Pohlmann | Statement: [Battle of Gawilghur, commander, Pohlmann]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Pohlmann
Context triple: [Battle of Gawilghur, commander, Pohlmann]
  • A. Pohlmann chosen
    Pohlmann was a European officer who became a senior commander in the Maratha army and led its forces against the British at the Battle of Assaye in 1803.
  • B. Pohl
    Pohl is a German surname borne by various notable individuals in fields such as literature, science, and politics.
  • C. Pfohl
    Pfohl is the surname of Lawrence Wendell "Lex Luger" Pfohl, an American professional wrestler best known for his time in WCW and WWF during the 1990s.
  • D. Paepcke
    Paepcke is a surname most notably associated with Walter Paepcke, the American industrialist and cultural philanthropist who founded the Aspen Institute.
  • E. Henselmann
    Henselmann is the surname of Hermann Henselmann, a prominent German architect known for his influential role in postwar East German architecture.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69d8dd01a56c81909694a128c66b21d7 completed April 10, 2026, 11:20 a.m.
NER Named-entity recognition batch_69e5d67dee4c8190ac2017ff748ea6aa completed April 20, 2026, 7:32 a.m.
Created at: April 10, 2026, 12:01 p.m.