Triple
T30056429
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kream |
E763744
|
entity |
| Predicate | platformOfVirality |
P68229
|
FINISHED |
| Object | social media |
—
|
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: social media | Statement: [Kream, platformOfVirality, social media]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: platformOfVirality Context triple: [Kream, platformOfVirality, social media]
-
A.
socialPhenomenon
Indicates a relationship where an event, behavior, or pattern emerges from and affects interactions within a society or group.
-
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.
socialMediaTrend
Indicates that something is currently popular, widely discussed, or rapidly spreading in visibility and engagement on social media platforms.
-
D.
videoPlatform
chosen
Indicates a relationship where an entity serves as or is associated with a platform used for hosting, sharing, or streaming video content.
-
E.
isPopularOnSocialMedia
Indicates that an entity is widely followed, frequently engaged with, or broadly recognized across social media platforms.
- 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_69f224716378819087a722e487832b70 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6afebd7ec8190ab696f363d84abf0 |
completed | May 3, 2026, 2:16 a.m. |
| PD | Predicate disambiguation | batch_69f6aca204148190850a3dc325bc07b7 |
completed | May 3, 2026, 2:02 a.m. |
Created at: April 29, 2026, 6:56 p.m.