Triple

T23705626
Position Surface form Disambiguated ID Type / Status
Subject Charles XII’s Russian campaign E585711 entity
Predicate opposingAlly P4567 FINISHED
Object Cossack forces loyal to Ivan Skoropadsky 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: Cossack forces loyal to Ivan Skoropadsky | Statement: [Charles XII’s Russian campaign, opposingAlly, Cossack forces loyal to Ivan Skoropadsky]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: opposingAlly
Context triple: [Charles XII’s Russian campaign, opposingAlly, Cossack forces loyal to Ivan Skoropadsky]
  • A. opposingAlliance
    Indicates that two entities belong to rival or mutually opposed alliances or factions.
  • B. formerAllyOf
    Indicates that an entity was once an ally of another entity but that alliance has since ended.
  • C. oppositionAlliance
    Indicates a relationship where entities form or belong to an alliance that is collectively opposed to another entity or group.
  • D. 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.
  • E. opposingForce chosen
    Indicates a relationship where one entity actively resists, counters, or works against the actions, goals, or influence of another entity.
  • 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_69e24904bd508190abfcb74855de2918 completed April 17, 2026, 2:51 p.m.
NER Named-entity recognition batch_69f1b686ef50819090a85e3ed40cfba1 completed April 29, 2026, 7:43 a.m.
PD Predicate disambiguation batch_69f155e4b1148190836ede4741dcb888 completed April 29, 2026, 12:50 a.m.
Created at: April 17, 2026, 6:53 p.m.