Triple

T34517782
Position Surface form Disambiguated ID Type / Status
Subject Battle of Puente de Calderón E886199 entity
Predicate strengthInsurgents P179660 FINISHED
Object approximately 80,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 80,000 men | Statement: [Battle of Puente de Calderón, strengthInsurgents, approximately 80,000 men]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: strengthInsurgents
Context triple: [Battle of Puente de Calderón, strengthInsurgents, approximately 80,000 men]
  • A. strengthGovernmentForces
    Indicates the level or degree of military or coercive power held or exerted by government forces in a given context.
  • B. combatantStrength
    Indicates the relative level of power, capability, or effectiveness one combatant has in a conflict or confrontation compared to others.
  • C. endedInsurgencyType
    Indicates the specific manner or category of outcome by which an insurgency was brought to an end.
  • D. commandingForce2Strength
    Indicates that a commanding force possesses or exerts a particular level or measure of strength.
  • E. commandingForce1Strength
    Indicates that one entity has a certain level or measure of strength in its role as the primary commanding force over another entity or situation.
  • 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_69f349ccc290819089d8e82698e53cb6 completed April 30, 2026, 12:23 p.m.
NER Named-entity recognition batch_69f7238172748190b8cd340ad1f4ba80 completed May 3, 2026, 10:29 a.m.
PD Predicate disambiguation batch_69f72155c48881909bd40b9aa3febd5a completed May 3, 2026, 10:20 a.m.
PDg Predicate description generation batch_69f72349f1108190b6a06758ab2f40bb completed May 3, 2026, 10:28 a.m.
Created at: May 1, 2026, 2:01 a.m.