Triple
T34663960
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United States genocide determination (2004) |
E890199
|
entity |
| Predicate | locationOfAtrocities |
P203355
|
FINISHED |
| Object | Darfur |
E256794
|
NE 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: Darfur | Statement: [United States genocide determination (2004), locationOfAtrocities, Darfur]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locationOfAtrocities Context triple: [United States genocide determination (2004), locationOfAtrocities, Darfur]
-
A.
countryOfAtrocities
chosen
Indicates the country within whose territory the atrocities occurred or were carried out.
-
B.
natureOfAtrocities
Indicates the specific type or character of atrocities associated with an event, action, or entity.
-
C.
massacreOccurredIn
Indicates that a massacre took place within the specified location or area.
-
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.
notableMassKillingSite
Indicates that a place is recognized as a significant location where a mass killing or massacre occurred.
- F. None of above.
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_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a387cee1af881909ab12d4093114295 |
completed | June 22, 2026, 12:08 a.m. |
| PD | Predicate disambiguation | batch_6a0379fd7aac8190873077e63873aa72 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 2:04 a.m.