Triple
T10282162
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Red Summer |
E241126
|
entity |
| Predicate | hasApproximateDeathToll |
P700
|
FINISHED |
| Object | hundreds of people killed |
—
|
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: hundreds of people killed | Statement: [Red Summer, hasApproximateDeathToll, hundreds of people killed]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasApproximateDeathToll Context triple: [Red Summer, hasApproximateDeathToll, hundreds of people killed]
-
A.
deathTollEstimate
chosen
Indicates an estimated number of deaths attributed to a particular event, cause, or period.
-
B.
deathToll
Indicates the number of deaths resulting from a particular event, situation, or cause.
-
C.
casualtiesEstimate
Indicates an estimated number of people killed, injured, or otherwise harmed as a result of an event or incident.
-
D.
militaryCasualtiesEstimate
Indicates an estimated number of people killed, wounded, or missing as a result of military conflict or operations.
-
E.
nativeCasualties
Indicates that native or indigenous people suffered deaths or injuries as a result of a particular event, action, or conflict.
- 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_69d381a94c1881908fc38fc263d9b9c2 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4d7ccb7ec8190a538cf279e48116e |
completed | April 7, 2026, 10:09 a.m. |
| PD | Predicate disambiguation | batch_69d4d1f117708190928f92ae2611d724 |
completed | April 7, 2026, 9:44 a.m. |
Created at: April 6, 2026, 11:39 a.m.