Triple
T22783173
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shether |
E563891
|
entity |
| Predicate | containsPersonalInsults |
P43876
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Shether, containsPersonalInsults, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsPersonalInsults Context triple: [Shether, containsPersonalInsults, yes]
-
A.
insultedAs
chosen
Indicates that one entity directed an insulting or offensive remark or action toward another entity, characterizing the target in a demeaning way.
-
B.
containsPersonalContent
Indicates that the referenced item includes content that is personal in nature, such as private details, sensitive information, or individually identifying material.
-
C.
hasPejorativeUsage
Indicates that the referenced term or expression is used in a disparaging, derogatory, or negative manner toward its subject.
-
D.
containsPanegyricsFor
Indicates that one entity includes or features elaborate praise or eulogistic content directed toward another entity.
-
E.
claimsInsultBy
Indicates that one entity asserts or alleges that another entity has insulted them.
- 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_69e2455500788190b4b33030461f3bbd |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17c2ee4e88190951afb2abe69009f |
completed | April 29, 2026, 3:34 a.m. |
| PD | Predicate disambiguation | batch_69eed2c32e8c8190b73bb9965ed47d64 |
completed | April 27, 2026, 3:06 a.m. |
Created at: April 17, 2026, 3:29 p.m.