Triple
T32802492
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Envolver |
E838932
|
entity |
| Predicate | platformWhereWentViral |
P7687
|
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: [Envolver, platformWhereWentViral, TikTok]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: platformWhereWentViral Context triple: [Envolver, platformWhereWentViral, TikTok]
-
A.
wentViralOn
chosen
Indicates that content rapidly spread and gained widespread attention or popularity on a particular platform or medium.
-
B.
isViral
Indicates that something spreads rapidly and widely through a population or network, often via person-to-person or user-to-user transmission.
-
C.
socialPhenomenon
Indicates a relationship where an event, behavior, or pattern emerges from and affects interactions within a society or group.
-
D.
videoPlatform
Indicates a relationship where an entity serves as or is associated with a platform used for hosting, sharing, or streaming video content.
-
E.
popularFor
Indicates that something is widely liked, recognized, or favored specifically because of a particular feature, quality, or use.
- 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_69f3493d35208190b4351b4e85f2fa16 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6e02ba6b881908dfafc52d3b75f1c |
completed | May 3, 2026, 5:42 a.m. |
| PD | Predicate disambiguation | batch_69f6de09c2f481909f8b2545d3208c9f |
completed | May 3, 2026, 5:32 a.m. |
Created at: May 1, 2026, 1:15 a.m.