Triple

T2532683
Position Surface form Disambiguated ID Type / Status
Subject Battle of Aughrim (1691) E56196 entity
Predicate WilliamiteStrength P39417 FINISHED
Object approximately 20,000–25,000 men 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 20,000–25,000 men | Statement: [Battle of Aughrim (1691), WilliamiteStrength, approximately 20,000–25,000 men]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: WilliamiteStrength
Context triple: [Battle of Aughrim (1691), WilliamiteStrength, approximately 20,000–25,000 men]
  • A. RoyalistForceStrength
    Indicates the size or level of military power possessed by a royalist-aligned force in a given context.
  • B. strengthBritishCavalry
    Indicates the numerical or qualitative level of military power or effectiveness possessed by British cavalry forces.
  • C. RoyalistArmyOutcome
    Indicates the result or consequence experienced by the Royalist army in a particular conflict or event.
  • D. strengthRussoAustrian
    Indicates the relative military or political strength between Russian and Austrian forces or interests in a given context.
  • E. RoyalistSide
    Indicates that an entity is aligned with, supports, or belongs to the faction favoring a monarchy or royal authority in a given conflict or context.
  • 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_69ab4a49b6508190bc467fbef4bac334 completed March 6, 2026, 9:42 p.m.
NER Named-entity recognition batch_69abd279cf108190b03fb6e0265f39d9 completed March 7, 2026, 7:23 a.m.
PD Predicate disambiguation batch_69abd0c2e34c8190a914d5c2afba147c completed March 7, 2026, 7:16 a.m.
PDg Predicate description generation batch_69abd18e72a88190bdcf12b326d42fad completed March 7, 2026, 7:19 a.m.
Created at: March 6, 2026, 9:47 p.m.