Triple

T32070120
Position Surface form Disambiguated ID Type / Status
Subject Battle of Tuyutí E818985 entity
Predicate commandersSide2 P187065 FINISHED
Object Paraguayan commanders 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: Paraguayan commanders | Statement: [Battle of Tuyutí, commandersSide2, Paraguayan commanders]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: commandersSide2
Context triple: [Battle of Tuyutí, commandersSide2, Paraguayan commanders]
  • A. commandersSide
    Indicates that one entity is on the same side, faction, or team as the commander in a conflict or competitive context.
  • B. commandersSide1
    Indicates that the referenced commander is aligned with or belongs to the first side/party in a conflict, competition, or opposing pair.
  • C. opposingCommanderSide
    Indicates that one commander is on the opposing or enemy side relative to another commander in a conflict or confrontation.
  • D. sideCommander
    Indicates that an entity serves as the commanding officer or leader in charge of a particular side or faction in a conflict, operation, or organization.
  • E. commandedSide
    Indicates that one entity served as the commanding side or force in relation to another entity, typically within a conflict, operation, or hierarchical command structure.
  • 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_69f348fecc088190af1470afe5a969f0 completed April 30, 2026, 12:20 p.m.
NER Named-entity recognition batch_69fb3425666081908916fcbf3b5dd907 completed May 6, 2026, 12:29 p.m.
PD Predicate disambiguation batch_69fb2f5f3164819099429c2cc3d24e01 completed May 6, 2026, 12:09 p.m.
PDg Predicate description generation batch_69fb3424724c8190ba55ecf66fa0b171 completed May 6, 2026, 12:29 p.m.
Created at: May 1, 2026, 12:23 a.m.