Triple
T233574
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nanjing Massacre |
E4459
|
entity |
| Predicate | typeOfAtrocities |
P7957
|
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: [Nanjing Massacre, typeOfAtrocities, mass executions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfAtrocities Context triple: [Nanjing Massacre, typeOfAtrocities, mass executions]
-
A.
listsAsGenocidalAct
Indicates that an entity classifies or designates something as an act of genocide.
-
B.
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).
-
C.
persecutedDuring
Indicates that one entity systematically harassed, oppressed, or victimized another entity during a specified time period or event.
-
D.
perpetratedBy
Indicates that an action, event, or wrongdoing was carried out or caused by a particular agent or entity.
-
E.
crimeType
chosen
Indicates the specific category or nature of the crime associated with an event or entity.
- 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_69a257363ffc81909757bde7ab3404da |
completed | Feb. 28, 2026, 2:47 a.m. |
| NER | Named-entity recognition | batch_69a25f14f72081908182e76300b59358 |
completed | Feb. 28, 2026, 3:20 a.m. |
| PD | Predicate disambiguation | batch_69a25b5c8c888190b5544e687736b373 |
completed | Feb. 28, 2026, 3:05 a.m. |
Created at: Feb. 28, 2026, 2:53 a.m.