Triple
T20777705
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Duékoué |
E511396
|
entity |
| Predicate | massacreDateApprox |
P141483
|
FINISHED |
| Object | March 2011 |
—
|
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: March 2011 | Statement: [Duékoué, massacreDateApprox, March 2011]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: massacreDateApprox Context triple: [Duékoué, massacreDateApprox, March 2011]
-
A.
massacreYear
Indicates the year in which a massacre event took place.
-
B.
massacreOccurred
Indicates that a large-scale, deliberate killing of multiple individuals took place in a specific event or context.
-
C.
massacreAlsoKnownAs
Indicates that a particular massacre is known or referred to by an alternative name or names.
-
D.
majorMassacre
Indicates a relationship where an event involves the large-scale, deliberate killing of many individuals, typically characterized by extreme violence and high casualty numbers.
-
E.
significantMassacre
Indicates that a massacre event is of notable scale, impact, or historical importance relative to other such events.
- 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_69e0b4cac7a48190a715cb3d545df2b4 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c26d34bc81908bb22087d434322d |
completed | April 21, 2026, 12:18 a.m. |
| PD | Predicate disambiguation | batch_69e5c0550ec481908a0877fb2409d983 |
completed | April 20, 2026, 5:57 a.m. |
| PDg | Predicate description generation | batch_69e5c3cbe5788190b7ace43bfdac2ef6 |
completed | April 20, 2026, 6:12 a.m. |
Created at: April 16, 2026, 12:37 p.m.