Triple
T31379820
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Emmett Till |
E800418
|
entity |
| Predicate | locationOfLynching |
P64889
|
FINISHED |
| Object | near Money, Leflore County, Mississippi, United States |
—
|
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: near Money, Leflore County, Mississippi, United States | Statement: [Emmett Till, locationOfLynching, near Money, Leflore County, Mississippi, United States]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locationOfLynching Context triple: [Emmett Till, locationOfLynching, near Money, Leflore County, Mississippi, United States]
-
A.
placeOfKilling
chosen
Indicates the location where a killing event took place.
-
B.
massacreOccurredIn
Indicates that a massacre took place within the specified location or area.
-
C.
notableMassKillingSite
Indicates that a place is recognized as a significant location where a mass killing or massacre occurred.
-
D.
notablePersonKilledThere
Indicates that a notable or famous person was killed at the referenced location.
-
E.
assassinationAttemptLocation
Indicates the place where an attempted assassination occurred or was intended to occur.
- 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_69f224e84da08190abfc2f17494a33c8 |
completed | April 29, 2026, 3:34 p.m. |
| NER | Named-entity recognition | batch_6a01839b071481909f9cc79a6a09387d |
completed | May 11, 2026, 7:22 a.m. |
| PD | Predicate disambiguation | batch_6a017edbed688190baa61cbae5110c8e |
completed | May 11, 2026, 7:01 a.m. |
Created at: April 29, 2026, 9:18 p.m.