Triple
T75817
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GenocideConvention1948 |
E1514
|
entity |
| Predicate | listsAsGenocidalAct |
P4723
|
FINISHED |
| Object | killing members of the group |
—
|
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: killing members of the group | Statement: [GenocideConvention1948, listsAsGenocidalAct, killing members of the group]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: listsAsGenocidalAct Context triple: [GenocideConvention1948, listsAsGenocidalAct, killing members of the group]
-
A.
notableVictim
Indicates that the subject is a person or entity who is notably recognized as a victim of the object (such as an event, crime, or harmful action).
-
B.
numberOfPeopleExecuted
Indicates the total count of individuals who were put to death, typically as a result of a formal execution process.
-
C.
usedMethodOfKilling
Indicates that one entity employed a particular method or means to carry out a killing of another entity.
-
D.
deathToll
Indicates the number of deaths resulting from a particular event, situation, or cause.
-
E.
numberOfPeoplePressedToDeath
Indicates the number of people who were killed specifically by being pressed to death.
- 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_69a24c60d19c8190a1b6c105ca59ef5b |
completed | Feb. 28, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69a25314bd6c81908d1cfd4b83f20049 |
completed | Feb. 28, 2026, 2:29 a.m. |
| PD | Predicate disambiguation | batch_69a24eae77ec81909015906f31f2b62e |
completed | Feb. 28, 2026, 2:10 a.m. |
| PDg | Predicate description generation | batch_69a25313f1688190ba0fa8677faaf65b |
completed | Feb. 28, 2026, 2:29 a.m. |
Created at: Feb. 28, 2026, 2:06 a.m.