Triple
T16142912
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pottawatomie massacre |
E391706
|
entity |
| Predicate | victimSide |
P121275
|
FINISHED |
| Object | pro-slavery settlers |
—
|
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: pro-slavery settlers | Statement: [Pottawatomie massacre, victimSide, pro-slavery settlers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: victimSide Context triple: [Pottawatomie massacre, victimSide, pro-slavery settlers]
-
A.
victimRole
Indicates that one entity participates in an event or situation specifically in the role of the victim or harmed party.
-
B.
victimParticipation
Indicates that the victim took part in, contributed to, or was otherwise involved in the event or action described.
-
C.
victimState
Indicates the condition or status that a victim is in as a result of an event, action, or harmful incident.
-
D.
victimLeader
Indicates that one entity is the primary target or sufferer (the victim) in a situation where another entity holds a leading or directing role in causing or overseeing that victimization.
-
E.
victimStatus
Indicates the condition or state of a person who has been harmed or wronged as a result of an event, action, or offense.
- 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_69d87f1c65e48190aa2b4c472e9bafc4 |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e21d9082588190bc7e6ff491f0d94e |
completed | April 17, 2026, 11:46 a.m. |
| PD | Predicate disambiguation | batch_69e182885bc08190822ae7e8a4b8ac1f |
completed | April 17, 2026, 12:44 a.m. |
| PDg | Predicate description generation | batch_69e1835b64948190ae1d2a9d4cc64acf |
completed | April 17, 2026, 12:48 a.m. |
Created at: April 10, 2026, 5:01 a.m.