Triple

T16546404
Position Surface form Disambiguated ID Type / Status
Subject Battle of Grochów E401952 entity
Predicate aimOfRussianSide P30325 FINISHED
Object crush the November Uprising 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: crush the November Uprising | Statement: [Battle of Grochów, aimOfRussianSide, crush the November Uprising]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: aimOfRussianSide
Context triple: [Battle of Grochów, aimOfRussianSide, crush the November Uprising]
  • A. RussoAustrianObjective
    Indicates a shared objective or goal jointly pursued by Russian and Austrian parties or forces.
  • B. SovietObjective
    Indicates that the entity represents a goal, target, or strategic aim pursued by the Soviet Union.
  • C. RussianObjective chosen
    Indicates that an entity has an objective, goal, or target specifically related to Russia (e.g., Russian interests, territory, institutions, or actors).
  • D. aimOfGermanForces
    Indicates that the specified objective or target is the intended goal or purpose of the actions undertaken by German military forces.
  • E. aimOfOtherSide
    Indicates that one party’s goal or intended outcome is directed toward or defined in relation to the opposing or counterpart side in a relationship or interaction.
  • 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_69d88384bc30819084229e7dcdc39a41 completed April 10, 2026, 4:58 a.m.
NER Named-entity recognition batch_69e34fbe3fb48190bad143b50dc73c7e completed April 18, 2026, 9:32 a.m.
PD Predicate disambiguation batch_69e2969fab208190ad64164d24748c45 completed April 17, 2026, 8:22 p.m.
Created at: April 10, 2026, 5:15 a.m.