Triple

T584769
Position Surface form Disambiguated ID Type / Status
Subject Battle of Leuthen E15134 entity
Predicate combatantStrengthPrussia P11878 FINISHED
Object approximately 36,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 36,000 soldiers | Statement: [Battle of Leuthen, combatantStrengthPrussia, approximately 36,000 soldiers]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: combatantStrengthPrussia
Context triple: [Battle of Leuthen, combatantStrengthPrussia, approximately 36,000 soldiers]
  • A. combatantStrength
    Indicates the relative level of power, capability, or effectiveness one combatant has in a conflict or confrontation compared to others.
  • B. warTimeStrengthApprox chosen
    Indicates an approximate measure of an entity’s military strength or capacity during a time of war.
  • C. countryOfDefeatedSide
    Indicates the country to which the losing or defeated side in a conflict, competition, or confrontation belongs.
  • D. troopStrengthAlliedApprox
    Indicates that the approximate troop strength of one entity is being assessed or reported in relation to its allied forces.
  • E. warPower
    Indicates the authority, capability, or legal power to initiate, conduct, or manage acts of war or armed conflict.
  • 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_69a4935783b8819082b77726ec10cc42 completed March 1, 2026, 7:28 p.m.
NER Named-entity recognition batch_69a49b9874c88190bd1e08d4689ea124 completed March 1, 2026, 8:03 p.m.
PD Predicate disambiguation batch_69a494c9315c8190a773e8e00737d8a0 completed March 1, 2026, 7:34 p.m.
Created at: March 1, 2026, 7:33 p.m.