Triple
T10986447
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 8chan |
E259641
|
entity |
| Predicate | reasonForDeplatforming |
P25587
|
FINISHED |
| Object | links to multiple mass shooting manifestos |
—
|
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: links to multiple mass shooting manifestos | Statement: [8chan, reasonForDeplatforming, links to multiple mass shooting manifestos]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reasonForDeplatforming Context triple: [8chan, reasonForDeplatforming, links to multiple mass shooting manifestos]
-
A.
censorshipReason
Indicates the justification or cause given for why certain content is suppressed, restricted, or removed.
-
B.
reasonForBan
chosen
Indicates the justification or cause that led to an entity being banned.
-
C.
reasonForDelisting
Indicates the specific cause or justification for which an item, entity, or record has been removed from a list or registry.
-
D.
platformSuspension
Indicates that an entity has been temporarily or permanently barred from accessing or using a particular platform or service.
-
E.
expulsionReason
Indicates the cause or justification for which an entity was expelled from a group, place, or institution.
- 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_69d6aa895f4c8190887a15460ef622f4 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d787b2e4a88190a81504eee77e2298 |
completed | April 9, 2026, 11:04 a.m. |
| PD | Predicate disambiguation | batch_69d72e9055908190b438f039574aaaaf |
completed | April 9, 2026, 4:44 a.m. |
Created at: April 8, 2026, 9:24 p.m.