Triple

T842386
Position Surface form Disambiguated ID Type / Status
Subject Battle of Jena–Auerstedt E18204 entity
Predicate PrussianStrength P20555 FINISHED
Object approximately 110000 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 110000 soldiers | Statement: [Battle of Jena–Auerstedt, PrussianStrength, approximately 110000 soldiers]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: PrussianStrength
Context triple: [Battle of Jena–Auerstedt, PrussianStrength, approximately 110000 soldiers]
  • A. PrussianCommander
    Indicates that an individual holds the position or role of a commander within the Prussian military forces.
  • B. PrussianObjective
    Indicates that an entity has the goal, target, or strategic objective of achieving or advancing something specifically related to Prussia or Prussian interests.
  • C. strengthRussoAustrian
    Indicates the relative military or political strength between Russian and Austrian forces or interests in a given context.
  • D. RussoAustrianObjective
    Indicates a shared objective or goal jointly pursued by Russian and Austrian parties or forces.
  • E. notableCommanderAxis
    Indicates that the subject entity had a notable military commander role or position on the Axis side in a conflict or war.
  • 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_69a4938b04208190b82e1df6b572c548 completed March 1, 2026, 7:29 p.m.
NER Named-entity recognition batch_69a4abe8a0bc81909b54af465e67be1f completed March 1, 2026, 9:13 p.m.
PD Predicate disambiguation batch_69a4aa7f396c8190aa8b8dfbe0b4f732 completed March 1, 2026, 9:07 p.m.
PDg Predicate description generation batch_69a4ab4893e481908632102d240466dc completed March 1, 2026, 9:10 p.m.
Created at: March 1, 2026, 7:38 p.m.