Triple
T22783175
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shether |
E563891
|
entity |
| Predicate | containsAllegations |
P83746
|
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, containsAllegations, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsAllegations Context triple: [Shether, containsAllegations, yes]
-
A.
hasAllegationsOf
chosen
Indicates that one entity is accused or suspected of engaging in certain actions, behaviors, or misconduct, but without implying that these accusations are proven.
-
B.
hasAllegedDetail
Indicates that an entity is associated with a detail or piece of information that is claimed or reported but not confirmed as factual.
-
C.
deniedAllegations
Indicates that one party has rejected or refuted specific accusations made against them.
-
D.
allegationByComplainant
Indicates that a specific allegation is made or asserted by the complainant against another party or situation.
-
E.
includesAllegedPerpetrators
Indicates that the subject entity contains or references individuals or groups identified as alleged perpetrators of an act or incident.
- 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.