Triple
T30692906
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Love Again |
E781377
|
entity |
| Predicate | usesPopSongStructure |
P63463
|
FINISHED |
| Object | verse-chorus-bridge |
—
|
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: verse-chorus-bridge | Statement: [Love Again, usesPopSongStructure, verse-chorus-bridge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesPopSongStructure Context triple: [Love Again, usesPopSongStructure, verse-chorus-bridge]
-
A.
isPopularSongFor
Indicates that a song is widely liked, well-known, or frequently chosen by a particular audience, group, or context.
-
B.
isPopularSongFrom
Indicates that a song is widely liked, well-known, or frequently played and originates from a particular source, such as an artist, album, or media work.
-
C.
isPopularSongOf
Indicates that a song is widely liked, well-known, or frequently enjoyed in relation to a particular entity (such as an artist, album, or context).
-
D.
isPopularSong
Indicates that a song is widely liked, well-known, or frequently listened to by many people.
-
E.
hasVerseChorusStructure
chosen
Indicates that something, typically a musical composition, is organized using a recurring pattern of verses and choruses.
- 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_69f224ab24e08190991d6edb6df58e8b |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f757898fe48190b124dc7301672623 |
completed | May 3, 2026, 2:11 p.m. |
| PD | Predicate disambiguation | batch_69f754c484348190948d2a04ff228fb1 |
completed | May 3, 2026, 1:59 p.m. |
Created at: April 29, 2026, 8:33 p.m.