Triple
T16696450
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kid Cudi (Pissy Pamper) (leaked track) |
E405727
|
entity |
| Predicate | timePeriodOfViralPopularity |
P3813
|
FINISHED |
| Object | late 2010s |
—
|
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: late 2010s | Statement: [Kid Cudi (Pissy Pamper) (leaked track), timePeriodOfViralPopularity, late 2010s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timePeriodOfViralPopularity Context triple: [Kid Cudi (Pissy Pamper) (leaked track), timePeriodOfViralPopularity, late 2010s]
-
A.
popularInPeriod
chosen
Indicates that something is widely liked, used, or influential during a specified time period.
-
B.
wentViralOn
Indicates that content rapidly spread and gained widespread attention or popularity on a particular platform or medium.
-
C.
timePeriod
Indicates the specific span or interval of time during which an event, state, or relationship occurs or is valid.
-
D.
hasViralImpact
Indicates that an entity causes, contributes to, or is associated with rapid, wide-scale spread or influence, similar to how viral content propagates.
-
E.
timePeriodOfMajorOutbreak
Indicates the time span during which a major outbreak occurred or was most active.
- 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_69d8838db21081909589220fd71440a4 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e37eadc35881909fb0cc405a0e2fae |
completed | April 18, 2026, 12:53 p.m. |
| PD | Predicate disambiguation | batch_69e319bc73908190a0e38bc926b31f10 |
completed | April 18, 2026, 5:42 a.m. |
Created at: April 10, 2026, 5:19 a.m.