Triple

T5176304
Position Surface form Disambiguated ID Type / Status
Subject Battle of Helsingborg E116806 entity
Predicate aimOfDanishForces P62182 FINISHED
Object reconquest of Scania 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: reconquest of Scania | Statement: [Battle of Helsingborg, aimOfDanishForces, reconquest of Scania]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: aimOfDanishForces
Context triple: [Battle of Helsingborg, aimOfDanishForces, reconquest of Scania]
  • A. objectiveOfBritishForces
    Indicates that the referenced entity represents a goal, target, or mission that the British forces aim to achieve or act upon.
  • B. objectiveOfJapaneseForces
    Indicates that a specified target, goal, or aim is the military objective pursued by Japanese forces.
  • C. PrussianObjective
    Indicates that an entity has the goal, target, or strategic objective of achieving or advancing something specifically related to Prussia or Prussian interests.
  • D. aimOfAllies
    Indicates that one entity represents the shared goal or objective pursued collectively by a group of allied entities.
  • E. goalDuringWar
    Indicates that a particular goal or objective is pursued, exists, or is relevant during the time period of a war or armed conflict.
  • F. None of above. chosen

Provenance (4 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_69bd446140f08190becb93c61158f27f completed March 20, 2026, 12:58 p.m.
NER Named-entity recognition batch_69bd797349008190b87ad9d0d3eb667f completed March 20, 2026, 4:44 p.m.
PD Predicate disambiguation batch_69bd77b529948190b86671ebe43f4734 completed March 20, 2026, 4:37 p.m.
PDg Predicate description generation batch_69bd79251b548190918a1eb930e24c22 completed March 20, 2026, 4:43 p.m.
Created at: March 20, 2026, 1:45 p.m.