Triple

T21928958
Position Surface form Disambiguated ID Type / Status
Subject Battle of Siikajoki E541516 entity
Predicate combatantStrengthRussia P1404 FINISHED
Object approximately 3,000 soldiers 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: approximately 3,000 soldiers | Statement: [Battle of Siikajoki, combatantStrengthRussia, approximately 3,000 soldiers]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: combatantStrengthRussia
Context triple: [Battle of Siikajoki, combatantStrengthRussia, approximately 3,000 soldiers]
  • A. strengthRussia
    Indicates a relationship where a level, measure, or display of strength is attributed to or associated with Russia.
  • B. combatantStrength chosen
    Indicates the relative level of power, capability, or effectiveness one combatant has in a conflict or confrontation compared to others.
  • C. sovietStrength
    Indicates the level or degree of strength, power, or capability associated with the Soviet side in a given context or interaction.
  • D. commanderSideRussia
    Indicates that the commander is aligned with, fighting for, or acting on behalf of the Russian side in a conflict or military context.
  • E. SovietForceType
    Indicates that the entity is classified as a type or category of Soviet military force.
  • 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_69e0c47d74488190a15119108794a307 completed April 16, 2026, 11:14 a.m.
NER Named-entity recognition batch_69f123fcd08481909fecbb2cf0405933 completed April 28, 2026, 9:17 p.m.
PD Predicate disambiguation batch_69e6f5efc208819091ed2cf6841fa600 completed April 21, 2026, 3:58 a.m.
Created at: April 16, 2026, 7:47 p.m.