Triple
T14675360
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Back in Love |
E344623
|
entity |
| Predicate | hasPopularityStatus |
P97301
|
FINISHED |
| Object | hit song for Shine |
—
|
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: hit song for Shine | Statement: [Back in Love, hasPopularityStatus, hit song for Shine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPopularityStatus Context triple: [Back in Love, hasPopularityStatus, hit song for Shine]
-
A.
hasPopularityCharacteristic
chosen
Indicates that an entity possesses a particular attribute or quality related to its level or type of popularity.
-
B.
hasPopularityScope
Indicates that the popularity of an entity is evaluated or applicable within a specified scope, context, or audience.
-
C.
isPopularAs
Indicates that an entity is widely liked, well-known, or favored in a particular role, context, or capacity.
-
D.
isPopularAt
Indicates that an entity enjoys a high level of recognition, approval, or favor within a specified place, context, or time.
-
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_69d822e283fc8190a0e4c235cf880052 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb5666e648190b5faa07076f497b8 |
completed | April 14, 2026, 9:45 p.m. |
| PD | Predicate disambiguation | batch_69de6579fb7881909becc8f5822b39d4 |
completed | April 14, 2026, 4:04 p.m. |
Created at: April 10, 2026, 1:27 a.m.