Triple

T6584603
Position Surface form Disambiguated ID Type / Status
Subject Derg E159188 entity
Predicate significantHumanRightsAbuses P16958 FINISHED
Object mass executions 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: mass executions | Statement: [Derg, significantHumanRightsAbuses, mass executions]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: significantHumanRightsAbuses
Context triple: [Derg, significantHumanRightsAbuses, mass executions]
  • A. humanRightsConcern
    Indicates a situation, action, or condition that raises issues related to the recognition, protection, or violation of human rights.
  • B. humanRightsSituation
    Indicates the overall condition, treatment, and respect for individuals’ fundamental rights and freedoms within a given context or jurisdiction.
  • C. associatedWithCrimesAgainstHumanity chosen
    Indicates a relationship in which an entity is linked or connected to the planning, commission, support, or responsibility for crimes against humanity.
  • D. hasRegionWithIntensePersecution
    Indicates that an entity includes or is associated with a geographic area where persecution is especially severe or intense.
  • E. methodOfPersecution
    Indicates the specific means, technique, or process by which an act of persecution is carried out.
  • 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_69c688366ce8819083f8883983c0df92 completed March 27, 2026, 1:37 p.m.
NER Named-entity recognition batch_69c6c07cdf048190945ca5810fb1de88 completed March 27, 2026, 5:38 p.m.
PD Predicate disambiguation batch_69c6acfb462481909cb7aff5af4bca9d completed March 27, 2026, 4:14 p.m.
Created at: March 27, 2026, 1:54 p.m.