Triple

T34663961
Position Surface form Disambiguated ID Type / Status
Subject United States genocide determination (2004) E890199 entity
Predicate countryOfAtrocities P203355 FINISHED
Object Sudan 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: Sudan | Statement: [United States genocide determination (2004), countryOfAtrocities, Sudan]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: countryOfAtrocities
Context triple: [United States genocide determination (2004), countryOfAtrocities, Sudan]
  • A. natureOfAtrocities
    Indicates the specific type or character of atrocities associated with an event, action, or entity.
  • B. massacreOccurredIn
    Indicates that a massacre took place within the specified location or area.
  • C. warCrimesContext
    Indicates a context in which actions or events are associated with the commission, investigation, or adjudication of war crimes.
  • D. relatedMassAtrocityContext
    Indicates that an entity is connected to, associated with, or occurs within the broader circumstances or environment of a mass atrocity event.
  • E. hasRegionWithIntensePersecution
    Indicates that an entity includes or is associated with a geographic area where persecution is especially severe or intense.
  • F. None of above. chosen

Provenance (4 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_69f349d906bc8190b2efd9eff237d94b completed April 30, 2026, 12:23 p.m.
NER Named-entity recognition batch_6a016777257081908841c5522dfa76e6 completed May 11, 2026, 5:21 a.m.
PD Predicate disambiguation batch_6a0164e49bec8190af3c8626be9677a9 completed May 11, 2026, 5:11 a.m.
PDg Predicate description generation batch_6a016775df2c81909448a0201f5f4af6 completed May 11, 2026, 5:21 a.m.
Created at: May 1, 2026, 2:04 a.m.