Triple

T28919657
Position Surface form Disambiguated ID Type / Status
Subject POUM E733471 entity
Predicate wasRepressedBy P131709 FINISHED
Object Spanish Republican government NE NERFINISHED

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: Spanish Republican government | Statement: [POUM, wasRepressedBy, Spanish Republican government]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: wasRepressedBy
Context triple: [POUM, wasRepressedBy, Spanish Republican government]
  • A. associatedWithRepressionSystem chosen
    Indicates that an entity is connected to, involved in, or part of a system or mechanism used for repression or suppressive control.
  • B. forcedBy
    Indicates that an entity is compelled or coerced into an action or state by another entity.
  • C. suppressedOn
    Indicates that one entity is intentionally prevented, hidden, or blocked from being shown, executed, or taking effect in the context of another entity.
  • D. suppressedAsPartOf
    Indicates that one entity is intentionally prevented, hidden, or constrained as a component or subset of a broader suppression involving another entity.
  • E. isReleasedInResponseTo
    Indicates that an action, statement, or item is issued or made available as a direct reaction to a specific event, condition, or stimulus.
  • 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_69f05b0a5cc0819094828367ae204b70 completed April 28, 2026, 7 a.m.
NER Named-entity recognition batch_69f65b18c1208190add0150dd5e95270 completed May 2, 2026, 8:14 p.m.
PD Predicate disambiguation batch_69f6576487e081908d802f1caf59c423 completed May 2, 2026, 7:58 p.m.
Created at: April 28, 2026, 8:18 a.m.