Triple

T5106345
Position Surface form Disambiguated ID Type / Status
Subject Battle of Selby E115103 entity
Predicate combatantStrengthRoyalist P20427 FINISHED
Object approximately 1,500–2,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 1,500–2,000 men | Statement: [Battle of Selby, combatantStrengthRoyalist, approximately 1,500–2,000 men]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: combatantStrengthRoyalist
Context triple: [Battle of Selby, combatantStrengthRoyalist, approximately 1,500–2,000 men]
  • A. RoyalistForceStrength chosen
    Indicates the size or level of military power possessed by a royalist-aligned force in a given context.
  • B. 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.
  • C. primaryRoyalistCavalryLeader
    Indicates that someone serves as the main commanding leader of cavalry forces aligned with the Royalist side.
  • D. RoyalistArmyOutcome
    Indicates the result or consequence experienced by the Royalist army in a particular conflict or event.
  • E. combatantStrength
    Indicates the relative level of power, capability, or effectiveness one combatant has in a conflict or confrontation compared to others.
  • 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_69bd4440b3348190be1251fd8b7951f1 completed March 20, 2026, 12:57 p.m.
NER Named-entity recognition batch_69bd75a7c6748190b02b7c2b617c830f completed March 20, 2026, 4:28 p.m.
PD Predicate disambiguation batch_69bd715fe3a8819087d3065adddba515 completed March 20, 2026, 4:10 p.m.
Created at: March 20, 2026, 1:41 p.m.