Triple
T29068959
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shaky Shaky |
E735760
|
entity |
| Predicate | becameViral |
P127952
|
FINISHED |
| Object | Yes |
—
|
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: Yes | Statement: [Shaky Shaky, becameViral, Yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: becameViral Context triple: [Shaky Shaky, becameViral, Yes]
-
A.
wentViralOn
Indicates that content rapidly spread and gained widespread attention or popularity on a particular platform or medium.
-
B.
isViral
chosen
Indicates that something spreads rapidly and widely through a population or network, often via person-to-person or user-to-user transmission.
-
C.
hasViralImpact
Indicates that an entity causes, contributes to, or is associated with rapid, wide-scale spread or influence, similar to how viral content propagates.
-
D.
socialPhenomenon
Indicates a relationship where an event, behavior, or pattern emerges from and affects interactions within a society or group.
-
E.
hasViralMusicVideo
Indicates that an entity possesses or is associated with a music video that has achieved viral popularity or widespread online circulation.
- 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_69f077e9b0a48190bb79548279cb7f64 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f6645ba71c81908044ade6ab577018 |
completed | May 2, 2026, 8:53 p.m. |
| PD | Predicate disambiguation | batch_69f663362c008190a22afed262f1e426 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 28, 2026, 10:19 a.m.