Triple

T582255
Position Surface form Disambiguated ID Type / Status
Subject Home Army E15082 entity
Predicate repressedBy P10731 FINISHED
Object communist authorities in postwar Poland 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: communist authorities in postwar Poland | Statement: [Home Army, repressedBy, communist authorities in postwar Poland]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: repressedBy
Context triple: [Home Army, repressedBy, communist authorities in postwar Poland]
  • A. forcedBy
    Indicates that an entity is compelled or coerced into an action or state by another entity.
  • B. opposedBy
    Indicates that one entity actively resists, disagrees with, or works against the actions, views, or position of another entity.
  • C. suppressedDuring chosen
    Indicates that one event, action, or state is actively prevented, inhibited, or held back while another specified event, condition, or time period is occurring.
  • D. relievedBy
    Indicates that one entity eases, reduces, or removes the burden, pain, stress, or responsibility experienced by another entity.
  • E. restriction
    Indicates a limiting condition or rule that constrains or controls what an entity can do, use, or access in relation to another entity or context.
  • 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_69a4935783b8819082b77726ec10cc42 completed March 1, 2026, 7:28 p.m.
NER Named-entity recognition batch_69a49b85becc8190b4d98c00e5fa7c04 completed March 1, 2026, 8:03 p.m.
PD Predicate disambiguation batch_69a494c7f9008190bd8d05b4dc2a7c7f completed March 1, 2026, 7:34 p.m.
Created at: March 1, 2026, 7:33 p.m.