Triple
T22189687
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | "Bye, Felicia" |
E548383
|
entity |
| Predicate | becameMemeIn |
P138751
|
FINISHED |
| Object | late 2000s |
—
|
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 2000s | Statement: ["Bye, Felicia", becameMemeIn, late 2000s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: becameMemeIn Context triple: ["Bye, Felicia", becameMemeIn, late 2000s]
-
A.
becameCatchphraseIn
chosen
Indicates that a phrase or expression came to be widely recognized and used as a catchphrase within a particular context, group, or time period.
-
B.
became
Indicates a change of state or status in which one entity transitions into or assumes the role, condition, or identity of another.
-
C.
gainedProminenceAs
Indicates that an entity became widely recognized or notable in the role, capacity, or identity specified by another entity.
-
D.
relocatedAndBecame
Indicates that an entity moved from one place to another and, as a result of this move, assumed a new role, status, or identity.
-
E.
wentViralOn
Indicates that content rapidly spread and gained widespread attention or popularity on a particular platform or medium.
- 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_69e11e3e0c7c8190b30d278845e2497e |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f12aac07d88190848c940863c0a0c7 |
completed | April 28, 2026, 9:46 p.m. |
| PD | Predicate disambiguation | batch_69e71b48576c8190a8e93738fd9cfda5 |
completed | April 21, 2026, 6:38 a.m. |
Created at: April 16, 2026, 8:35 p.m.