Triple
T17476015
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | After Party |
E425539
|
entity |
| Predicate | isViralOnTikTok |
P7687
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [After Party, isViralOnTikTok, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isViralOnTikTok Context triple: [After Party, isViralOnTikTok, true]
-
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.
wentViralOn
chosen
Indicates that content rapidly spread and gained widespread attention or popularity on a particular platform or medium.
-
C.
isPopularOnSocialMedia
Indicates that an entity is widely followed, frequently engaged with, or broadly recognized across social media platforms.
-
D.
hasViralMusicVideo
Indicates that an entity possesses or is associated with a music video that has achieved viral popularity or widespread online circulation.
-
E.
hasTrend
Indicates that something exhibits or is associated with a particular pattern of change or direction over time.
- 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_69d889dbc2e88190b18ea6115e819258 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e451bb7050819080e3873bcc8a950c |
completed | April 19, 2026, 3:53 a.m. |
| PD | Predicate disambiguation | batch_69e3b4f341c88190adabe526d8903b05 |
completed | April 18, 2026, 4:44 p.m. |
Created at: April 10, 2026, 5:47 a.m.