Triple
T20152922
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Game Grumps |
E491480
|
entity |
| Predicate | channelCategory |
P138872
|
FINISHED |
| Object | gaming |
—
|
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: gaming | Statement: [Game Grumps, channelCategory, gaming]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: channelCategory Context triple: [Game Grumps, channelCategory, gaming]
-
A.
channels
Indicates that one entity serves as a medium, route, or conduit through which another entity is directed, transmitted, or delivered.
-
B.
originalChannelCategory
Indicates the category or type of channel an item or communication originally belonged to before any changes or reclassification.
-
C.
channelSpecialization
Indicates that one channel is a more specialized or focused version of another, typically refining or narrowing the scope of the broader channel.
-
D.
fictionalChannelCategory
Indicates that a communication channel belongs to a category that exists only in a fictional or imagined context.
-
E.
navigationCategory
Indicates that one entity is classified under, or associated with, a particular navigation-related category used for organizing or guiding access to content or locations.
- 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_69da6265f8f0819080b29c752a574088 |
completed | April 11, 2026, 3:01 p.m. |
| NER | Named-entity recognition | batch_69e667dda9b4819097ff66bb2b50fc21 |
completed | April 20, 2026, 5:52 p.m. |
| PD | Predicate disambiguation | batch_69e54cfd924881909b55f3e4d3e7e070 |
completed | April 19, 2026, 9:45 p.m. |
| PDg | Predicate description generation | batch_69e54fc2bc3c819088c33cd263303433 |
completed | April 19, 2026, 9:57 p.m. |
Created at: April 11, 2026, 11:34 p.m.