Triple

T1753035
Position Surface form Disambiguated ID Type / Status
Subject Battle of the Dnieper E38489 entity
Predicate estimatedForcesEngaged P6153 FINISHED
Object over 4,000,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: over 4,000,000 soldiers | Statement: [Battle of the Dnieper, estimatedForcesEngaged, over 4,000,000 soldiers]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: estimatedForcesEngaged
Context triple: [Battle of the Dnieper, estimatedForcesEngaged, over 4,000,000 soldiers]
  • A. numberOfTroopsInvolved chosen
    Indicates the quantity of military personnel participating in or assigned to a specific operation, event, or engagement.
  • B. combatantStrength
    Indicates the relative level of power, capability, or effectiveness one combatant has in a conflict or confrontation compared to others.
  • C. besiegingForce
    Indicates a military group that is surrounding and attacking a target location or force in an attempt to capture or subdue it.
  • D. troopStrengthAlliedApprox
    Indicates that the approximate troop strength of one entity is being assessed or reported in relation to its allied forces.
  • E. militaryCasualtiesEstimate
    Indicates an estimated number of people killed, wounded, or missing as a result of military conflict or operations.
  • 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_69a8862bdb2081908aefe831c8aa8017 completed March 4, 2026, 7:21 p.m.
NER Named-entity recognition batch_69aba6a63f588190b53b39c6b97d74f4 completed March 7, 2026, 4:16 a.m.
PD Predicate disambiguation batch_69aa61c7ef4c8190abec87c96a787d82 completed March 6, 2026, 5:10 a.m.
Created at: March 4, 2026, 7:31 p.m.