Triple
T16082655
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | It's Gonna Be Me |
E390146
|
entity |
| Predicate | internetMemePhrase |
P66537
|
FINISHED |
| Object | It’s gonna be May |
—
|
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: It’s gonna be May | Statement: [It's Gonna Be Me, internetMemePhrase, It’s gonna be May]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: internetMemePhrase Context triple: [It's Gonna Be Me, internetMemePhrase, It’s gonna be May]
-
A.
meaningOfPhrase
Indicates that one entity expresses or defines the semantic content or interpretation of a given phrase.
-
B.
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).
-
C.
inspiredByPhrase
Indicates that one entity’s creation, idea, or expression is motivated or shaped by the content or wording of a particular phrase.
-
D.
featuresCatchphrase
Indicates that an entity prominently includes or is associated with a particular catchphrase.
-
E.
usedPhrase
Indicates that one entity employed or expressed a particular phrase in speech, writing, or another form of communication.
- 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_69d87f198bc48190a8b7e53ca15b7ead |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e1ff63edb0819092cbb671967bbdcd |
completed | April 17, 2026, 9:37 a.m. |
| PD | Predicate disambiguation | batch_69e1827ad7c88190b867da511cbfb7fa |
completed | April 17, 2026, 12:44 a.m. |
Created at: April 10, 2026, 4:59 a.m.