Triple
T36070623
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Catch Me Outside |
E1043353
|
entity |
| Predicate | hasMemeInfluence |
P66537
|
FINISHED |
| Object | internet culture |
—
|
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: internet culture | Statement: [Catch Me Outside, hasMemeInfluence, internet culture]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMemeInfluence Context triple: [Catch Me Outside, hasMemeInfluence, internet culture]
-
A.
hasMemeFormat
Indicates that one entity serves as the template or structural pattern used to create memes involving another entity.
-
B.
hasMemeStatusBy
Indicates that an entity possesses or is assigned a particular meme-related status as determined or conferred by another entity.
-
C.
hasLyricMeme
Indicates that one entity is associated with a meme derived from or based on the lyrics of another entity (typically a song).
-
D.
associatedMeme
chosen
Indicates that one entity is linked or connected to another entity in the context of a meme (e.g., as its related or corresponding meme).
-
E.
hasPopularityInfluencedBy
Indicates that the popularity level of one entity is affected or shaped by another specified factor or entity.
- 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_69f76e2fd3248190b900d9a492bf5a7a |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69ff49016dcc8190a8a43868c728b4f1 |
completed | May 9, 2026, 2:47 p.m. |
| PD | Predicate disambiguation | batch_69ff4891924c8190b5be340e2520e012 |
completed | May 9, 2026, 2:45 p.m. |
Created at: May 3, 2026, 4:08 p.m.