Triple
T8067059
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | I Don't Like |
E188268
|
entity |
| Predicate | becameInternetMeme |
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: [I Don't Like, becameInternetMeme, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: becameInternetMeme Context triple: [I Don't Like, becameInternetMeme, true]
-
A.
wentViralOn
chosen
Indicates that content rapidly spread and gained widespread attention or popularity on a particular platform or medium.
-
B.
associatedMeme
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).
-
C.
became
Indicates a change of state or status in which one entity transitions into or assumes the role, condition, or identity of another.
-
D.
popularizedAfter
Indicates that one entity became widely known, accepted, or influential only after another specified entity had already gained popularity.
-
E.
popularizedBy
Indicates that something became widely known, accepted, or fashionable as a result of the influence or actions of a particular agent.
- 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_69ca82b42674819086840efea12478e5 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3ff75d208190b7c53d2fe55878ac |
completed | March 31, 2026, 3:31 a.m. |
| PD | Predicate disambiguation | batch_69cb049cd51c8190bb3b0f503e42fa8d |
completed | March 30, 2026, 11:17 p.m. |
Created at: March 30, 2026, 5:26 p.m.