Triple

T2558594
Position Surface form Disambiguated ID Type / Status
Subject Battle of Benburb E56786 entity
Predicate strengthSide2 P30658 FINISHED
Object approximately 6,000–7,000 Scottish and allied troops 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 6,000–7,000 Scottish and allied troops | Statement: [Battle of Benburb, strengthSide2, approximately 6,000–7,000 Scottish and allied troops]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: strengthSide2
Context triple: [Battle of Benburb, strengthSide2, approximately 6,000–7,000 Scottish and allied troops]
  • A. strengthDescription
    Indicates a description or characterization of the degree of strength associated with an entity or relationship.
  • B. strength
    Indicates the degree of power, intensity, or effectiveness with which an entity can act on, influence, or withstand another entity or force.
  • C. opponentStrength chosen
    Indicates the level or degree of power, skill, or capability possessed by an opposing party in a competitive or adversarial context.
  • D. isStrongerThan
    Indicates that one entity possesses greater physical power, force, or effectiveness than another entity.
  • E. strengthPeak
    Indicates the point or period at which an entity’s strength reaches its maximum level.
  • 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_69ab4a4bfec081908039988ec4c86e28 completed March 6, 2026, 9:42 p.m.
NER Named-entity recognition batch_69abd35c6ee88190b6eaa1841d3e99a4 completed March 7, 2026, 7:27 a.m.
PD Predicate disambiguation batch_69abd0caeb488190b0dd8e48d0f2777d completed March 7, 2026, 7:16 a.m.
Created at: March 6, 2026, 9:48 p.m.