Triple
T26021075
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Twitch Bits |
E647153
|
entity |
| Predicate | hasActionName |
P165019
|
FINISHED |
| Object | Cheer |
—
|
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: Cheer | Statement: [Twitch Bits, hasActionName, Cheer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasActionName Context triple: [Twitch Bits, hasActionName, Cheer]
-
A.
hasActionType
Indicates that an action or event is classified as belonging to a specific type or category of actions.
-
B.
hasPageAction
Indicates that a specific action or operation is associated with, or can be performed on, a particular page.
-
C.
hasKeyAction
Indicates that an entity performs or is associated with a primary or essential action within a given context.
-
D.
hasOwnerAction
Indicates that an owner performs, initiates, or is responsible for a specific action related to the owned entity.
-
E.
hasRouteName
Indicates that a route, path, or connection is associated with a specific name or label.
- F. None of above. chosen
Provenance (4 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_69f65705a3048190a3728b695ba2ae65 |
completed | May 2, 2026, 7:56 p.m. |
| PD | Predicate disambiguation | batch_69f651a731508190bb0c8c2462eba224 |
completed | May 2, 2026, 7:33 p.m. |
| PDg | Predicate description generation | batch_69f6562ef4e4819082ce6abd41b74dc5 |
completed | May 2, 2026, 7:53 p.m. |
Created at: April 22, 2026, 9:03 a.m.