Triple

T20905553
Position Surface form Disambiguated ID Type / Status
Subject Battle of Pasco E514787 entity
Predicate opposingForceRole P6060 FINISHED
Object royalist troops defending Spanish authority in Peru 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: royalist troops defending Spanish authority in Peru | Statement: [Battle of Pasco, opposingForceRole, royalist troops defending Spanish authority in Peru]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: opposingForceRole
Context triple: [Battle of Pasco, opposingForceRole, royalist troops defending Spanish authority in Peru]
  • A. opposingForce
    Indicates a relationship where one entity actively resists, counters, or works against the actions, goals, or influence of another entity.
  • B. opposingAlliance
    Indicates that two entities belong to rival or mutually opposed alliances or factions.
  • C. opposingCommander
    Indicates that one entity serves as the commanding officer of a force that is in opposition or conflict with the force commanded by another entity.
  • D. opposingCommanderSide
    Indicates that one commander is on the opposing or enemy side relative to another commander in a conflict or confrontation.
  • E. conflictRole chosen
    Indicates that an entity plays a specific role or position within a conflict or dispute between parties.
  • 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_69e0b4f8a1108190bce3d31331290ced completed April 16, 2026, 10:07 a.m.
NER Named-entity recognition batch_69e6e8ff36488190987ecdfcbed4220c completed April 21, 2026, 3:03 a.m.
PD Predicate disambiguation batch_69e5c9ac91108190a6700fcdf2f11890 completed April 20, 2026, 6:37 a.m.
Created at: April 16, 2026, 12:47 p.m.