Triple

T573470
Position Surface form Disambiguated ID Type / Status
Subject Battle of Malplaquet E13711 entity
Predicate AlliedStrength P690 FINISHED
Object approximately 86,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 86,000 soldiers | Statement: [Battle of Malplaquet, AlliedStrength, approximately 86,000 soldiers]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: AlliedStrength
Context triple: [Battle of Malplaquet, AlliedStrength, approximately 86,000 soldiers]
  • A. troopStrengthAlliedApprox chosen
    Indicates that the approximate troop strength of one entity is being assessed or reported in relation to its allied forces.
  • B. mainAlliedPower
    Indicates that an entity serves as a primary or leading ally to another entity within an alliance or coalition.
  • C. alliance
    Indicates a formal cooperative relationship between entities who agree to support each other in shared goals or interests.
  • D. allianceSupport
    Indicates a cooperative relationship where one party provides assistance, resources, or backing to an ally within the context of an alliance.
  • E. alliedVictoryIn
    Indicates that the subject participated in or contributed to a military or strategic victory achieved by an alliance or coalition in the specified context.
  • 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_69a4933fa4d88190a7949cc83c08c5c1 completed March 1, 2026, 7:27 p.m.
NER Named-entity recognition batch_69a49b4ae0988190bdd0ad428b784d85 completed March 1, 2026, 8:02 p.m.
PD Predicate disambiguation batch_69a494c4969c819080375d08f9eec50c completed March 1, 2026, 7:34 p.m.
Created at: March 1, 2026, 7:33 p.m.