Triple
T31308988
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Carolyn Bryant Donham |
E798410
|
entity |
| Predicate | accusedEmmettTillOf |
P9856
|
FINISHED |
| Object | improper conduct in 1955 |
—
|
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: improper conduct in 1955 | Statement: [Carolyn Bryant Donham, accusedEmmettTillOf, improper conduct in 1955]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: accusedEmmettTillOf Context triple: [Carolyn Bryant Donham, accusedEmmettTillOf, improper conduct in 1955]
-
A.
roleInEmmettTillCase
Indicates that one entity had a specific role or involvement in the historical case surrounding Emmett Till.
-
B.
accusedOf
chosen
Indicates that one entity has formally alleged or claimed that another entity committed a specific wrongdoing or offense.
-
C.
allegedToHaveKilled
Indicates that one entity is claimed or accused, but not proven, to have killed another entity.
-
D.
accusedIn
Indicates that a person or entity is formally charged with wrongdoing in a particular case, proceeding, or context.
-
E.
wronglyAccusedBy
Indicates that one entity has falsely or unjustly accused another entity of wrongdoing.
- 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_69f224e1932c81908fef14f7b03a10b7 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69edbb7648190bd89c57e0932eac1 |
completed | May 3, 2026, 1:03 a.m. |
| PD | Predicate disambiguation | batch_69f69d1bf8cc8190a78dfa5ab00daf3a |
completed | May 3, 2026, 12:55 a.m. |
Created at: April 29, 2026, 9:15 p.m.