Triple
T20152890
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ross O’Donovan |
E491479
|
entity |
| Predicate | notableOnlineCommunity |
P4150
|
FINISHED |
| Object | Game Grumps fanbase |
—
|
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: Game Grumps fanbase | Statement: [Ross O’Donovan, notableOnlineCommunity, Game Grumps fanbase]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableOnlineCommunity Context triple: [Ross O’Donovan, notableOnlineCommunity, Game Grumps fanbase]
-
A.
notableCommunity
Indicates that an entity is a particularly prominent or significant member of a given community.
-
B.
notableUserCommunity
Indicates that a user has a significant or distinguished presence, role, or recognition within a particular community.
-
C.
notableOnlinePresence
Indicates that an entity maintains a significant, recognizable, or influential presence in online platforms or digital media.
-
D.
hasOnlineCommunity
chosen
Indicates that an entity maintains or is associated with a community that interacts primarily through online platforms or digital channels.
-
E.
notableCommunityAffected
Indicates that a particular community of notable significance is directly impacted or influenced by the subject.
- 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_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. |
Created at: April 11, 2026, 11:34 p.m.