Triple
T36778069
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ain't Shit |
E908687
|
entity |
| Predicate | hasViralPlatform |
P57
|
FINISHED |
| Object | TikTok |
—
|
NE NERFINISHED |
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: TikTok | Statement: [Ain't Shit, hasViralPlatform, TikTok]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasViralPlatform Context triple: [Ain't Shit, hasViralPlatform, TikTok]
-
A.
hasViralImpact
Indicates that an entity causes, contributes to, or is associated with rapid, wide-scale spread or influence, similar to how viral content propagates.
-
B.
hasViralOrigin
Indicates that something originates from, is caused by, or is derived from a virus.
-
C.
hasViralMusicVideo
Indicates that an entity possesses or is associated with a music video that has achieved viral popularity or widespread online circulation.
-
D.
isViral
Indicates that something spreads rapidly and widely through a population or network, often via person-to-person or user-to-user transmission.
-
E.
hasOnlinePlatform
chosen
Indicates that an entity operates, maintains, or is associated with a presence or service on an online platform.
- 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_69f76e798aa08190ace31098d1b13e9f |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fd7b0503a08190ba07338365b6fcc9 |
completed | May 8, 2026, 5:56 a.m. |
| PD | Predicate disambiguation | batch_69fd7a9733dc81909199f453c0cc2bc1 |
completed | May 8, 2026, 5:54 a.m. |
Created at: May 3, 2026, 4:12 p.m.