Triple
T26021201
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Twitch Community Guidelines |
E647155
|
entity |
| Predicate | requireUsersTo |
P90349
|
FINISHED |
| Object | stay informed about changes |
—
|
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: stay informed about changes | Statement: [Twitch Community Guidelines, requireUsersTo, stay informed about changes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requireUsersTo Context triple: [Twitch Community Guidelines, requireUsersTo, stay informed about changes]
-
A.
requiredTo
chosen
Indicates that one entity has an obligation or necessity to perform an action or satisfy a condition in relation to another entity or context.
-
B.
requiredBy
Indicates that one entity depends on or cannot function properly without another entity being present, completed, or satisfied.
-
C.
requiresPass
Indicates that access to or participation in something is conditional on possessing a valid pass.
-
D.
requiresActionFrom
Indicates that one entity is obligated to perform or initiate some action in response to or as a consequence of another entity or situation.
-
E.
requires
Indicates that one entity must exist, occur, or be satisfied before another entity can exist, occur, or be carried out.
- 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_69f6b2a65c7c8190ac40f1466ceadefc |
completed | May 3, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69f6b14d7d508190bc7d4c89dfba4a32 |
completed | May 3, 2026, 2:22 a.m. |
Created at: April 22, 2026, 9:04 a.m.