Triple

T26874651
Position Surface form Disambiguated ID Type / Status
Subject Battle of Sumter’s Defeat E676712 entity
Predicate sideVictorious P15330 FINISHED
Object British forces under Banastre Tarleton 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: British forces under Banastre Tarleton | Statement: [Battle of Sumter’s Defeat, sideVictorious, British forces under Banastre Tarleton]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: sideVictorious
Context triple: [Battle of Sumter’s Defeat, sideVictorious, British forces under Banastre Tarleton]
  • A. victoriousSide chosen
    Indicates which participant or group emerged as the winner in a competitive or conflict situation.
  • B. partyVictorious
    Indicates that a particular party has won or prevailed in a contest, conflict, or competitive situation.
  • C. victoryIn
    Indicates that one entity achieves a win or success in a specific contest, event, or competitive context involving another entity.
  • D. victor
    Indicates that one entity is the winner or has prevailed over another in a contest, conflict, or competition.
  • E. victoryTarget
    Indicates that one entity is the intended opponent, objective, or condition that must be overcome or achieved for the other entity to attain victory.
  • 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_69eee9bb44988190b6e11652d028bc59 completed April 27, 2026, 4:44 a.m.
NER Named-entity recognition batch_69f61f1721b081908875cb210bee4d08 completed May 2, 2026, 3:58 p.m.
PD Predicate disambiguation batch_69f611ad2eb48190ac1ed0090f13f7a9 completed May 2, 2026, 3:01 p.m.
Created at: April 27, 2026, 5:34 a.m.