Triple
T33481215
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Charleston riot of 1919 |
E857477
|
entity |
| Predicate | oppressorGroup |
P151310
|
FINISHED |
| Object | white residents of Charleston |
—
|
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: white residents of Charleston | Statement: [Charleston riot of 1919, oppressorGroup, white residents of Charleston]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oppressorGroup Context triple: [Charleston riot of 1919, oppressorGroup, white residents of Charleston]
-
A.
opposedByGroup
Indicates that an action, proposal, or entity is met with opposition or resistance from a particular group.
-
B.
opponentGroup
Indicates that one group is in opposition or conflict with another group, typically as a rival, competitor, or adversary.
-
C.
hasOppressor
chosen
Indicates that one entity acts as an oppressor toward another, exerting unjust or abusive power or control over them.
-
D.
controlGroup
Indicates that one entity functions as the control group against which another condition, treatment, or experimental group is compared.
-
E.
isGroupUnder
Indicates that one group is organizationally or hierarchically subordinate to, or contained within, another group.
- 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_69f3497472508190b300ebd3fd402367 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6f8164698819090c1b471f1caa4c6 |
completed | May 3, 2026, 7:24 a.m. |
| PD | Predicate disambiguation | batch_69f6f6619404819084662aef1238261c |
completed | May 3, 2026, 7:16 a.m. |
Created at: May 1, 2026, 1:38 a.m.