Triple
T26021179
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Twitch Community Guidelines |
E647155
|
entity |
| Predicate | includePolicyOn |
P57657
|
FINISHED |
| Object | hate conduct and harassment |
—
|
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: hate conduct and harassment | Statement: [Twitch Community Guidelines, includePolicyOn, hate conduct and harassment]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includePolicyOn Context triple: [Twitch Community Guidelines, includePolicyOn, hate conduct and harassment]
-
A.
containsPolicyOn
chosen
Indicates that one entity includes, references, or incorporates a specific policy within it.
-
B.
integrationPolicy
Indicates the rules or strategy governing how separate components, systems, or processes are combined and made to work together.
-
C.
issuesPolicyOn
Indicates that an authority or organization formally creates, approves, or enacts a policy concerning a particular subject or domain.
-
D.
appliesPolicyOn
Indicates that one entity enforces, executes, or brings into effect a specific policy on another entity or context.
-
E.
incorporationPolicy
Indicates the rules or conditions under which one entity is formally integrated or merged into another entity or system.
- 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_69e77e8aa65881909ca58918f29ab2a0 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69fb3425666081908916fcbf3b5dd907 |
completed | May 6, 2026, 12:29 p.m. |
| PD | Predicate disambiguation | batch_69fb2f5f3164819099429c2cc3d24e01 |
completed | May 6, 2026, 12:09 p.m. |
Created at: April 22, 2026, 9:04 a.m.