Triple

T5360215
Position Surface form Disambiguated ID Type / Status
Subject Battle of Prague (1757) E103000 entity
Predicate forceStrengthPrussia P31239 FINISHED
Object approximately 115000 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 115000 soldiers | Statement: [Battle of Prague (1757), forceStrengthPrussia, approximately 115000 soldiers]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: forceStrengthPrussia
Context triple: [Battle of Prague (1757), forceStrengthPrussia, approximately 115000 soldiers]
  • A. PrussianStrengthApprox chosen
    Indicates an approximate assessment or estimation of the strength or power associated with Prussia in a given context.
  • B. PrussianStrength
    Indicates a relationship where an entity possesses or exhibits the military, political, or institutional power characteristic of Prussia.
  • C. strengthAustriaSaxony
    Indicates the relative military or political strength between Austria and Saxony in a given context.
  • D. mainOpponentOfPrussia
    Indicates that one entity serves as the primary adversary or principal opposing force to Prussia in a given conflict or rivalry.
  • E. commandStructurePrussia
    Indicates the hierarchical command relationships within the Prussian military or administrative structure.
  • 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_69bd43daa3e4819090b59d127db70e57 completed March 20, 2026, 12:55 p.m.
NER Named-entity recognition batch_69bd86588af081908c846fcde65724da completed March 20, 2026, 5:39 p.m.
PD Predicate disambiguation batch_69bd845f41f88190b75b8b64b9e41862 completed March 20, 2026, 5:31 p.m.
Created at: March 20, 2026, 2:02 p.m.