Triple

T26497071
Position Surface form Disambiguated ID Type / Status
Subject Battle of Kolding E669310 entity
Predicate armedForce2 P39448 FINISHED
Object Schleswig-Holstein insurgent forces 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: Schleswig-Holstein insurgent forces | Statement: [Battle of Kolding, armedForce2, Schleswig-Holstein insurgent forces]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: armedForce2
Context triple: [Battle of Kolding, armedForce2, Schleswig-Holstein insurgent forces]
  • A. armedForcesCategory
    Indicates the classification of a country's or group's military forces into a specific type or category (e.g., army, navy, air force, paramilitary).
  • B. groundForces
    Indicates that one entity deploys, commands, or involves military forces operating on land in relation to another entity or context.
  • C. militaryOrganization
    Indicates that an entity functions as, or is associated with, a structured armed forces or defense-related organization.
  • D. armedForcesInvolved chosen
    Indicates that the relationship or event involves the participation or presence of military or armed forces.
  • E. opposingMilitaryBranch
    Indicates that two military branches belong to opposing or enemy forces in a conflict or strategic context.
  • 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_69eeb319007081909642b414b114b35a completed April 27, 2026, 12:51 a.m.
NER Named-entity recognition batch_69f613573c548190a4a25a430a89fbf4 completed May 2, 2026, 3:08 p.m.
PD Predicate disambiguation batch_69f60b89cc048190a9feb24466006be0 completed May 2, 2026, 2:34 p.m.
Created at: April 27, 2026, 1:09 a.m.