Triple
T24297883
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Benee |
E606013
|
entity |
| Predicate | songGainedPopularityOn |
P152493
|
FINISHED |
| Object | Supalonely – TikTok |
—
|
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: Supalonely – TikTok | Statement: [Benee, songGainedPopularityOn, Supalonely – TikTok]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: songGainedPopularityOn Context triple: [Benee, songGainedPopularityOn, Supalonely – TikTok]
-
A.
songBecame
Indicates that one song transformed into, evolved into, or was reissued as another song, marking a change in its identity or version over time.
-
B.
achievedPopularityIn
chosen
Indicates that an entity became popular or widely recognized within a specified place, group, or context.
-
C.
gainedProminenceAs
Indicates that an entity became widely recognized or notable in the role, capacity, or identity specified by another entity.
-
D.
songMadeFamousBy
Indicates that a song became widely known or popular primarily through the performance, recording, or promotion of a particular artist or group.
-
E.
gainedProminenceFor
Indicates that an entity became widely recognized or notable specifically because of another entity, action, or achievement.
- 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_69e29549335881909cbf27adcaba1cf0 |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f2915ada688190aa9c4bdaa2f1617f |
completed | April 29, 2026, 11:16 p.m. |
| PD | Predicate disambiguation | batch_69f1c45c6ec081908401b69424428100 |
completed | April 29, 2026, 8:42 a.m. |
Created at: April 18, 2026, 12:09 a.m.