Triple
T21441285
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Heartbreaker |
E528943
|
entity |
| Predicate | adaptedLyricsFor |
P110957
|
FINISHED |
| Object | American market |
—
|
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: American market | Statement: [Heartbreaker, adaptedLyricsFor, American market]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: adaptedLyricsFor Context triple: [Heartbreaker, adaptedLyricsFor, American market]
-
A.
lyricsAdaptedFrom
chosen
Indicates that the lyrics of one work are derived, adapted, or modified from the lyrics of another pre-existing work.
-
B.
modifiedLyricsDetail
Indicates that the relationship specifies detailed information about how the original lyrics have been altered or modified.
-
C.
lyricText
Indicates that one entity is the lyrical content or words of a song or musical piece associated with another entity.
-
D.
lyricFunction
Indicates the role or purpose that a set of lyrics serves within a musical work or performance.
-
E.
lyricSetting
Indicates that one entity serves as the text or lyrics that are set to music or otherwise musically realized by another 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_69e0c4569fa081908101baa24f8745db |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69e8b7022a5081908d9ad5058cecb8e5 |
completed | April 22, 2026, 11:54 a.m. |
| PD | Predicate disambiguation | batch_69e61639ee288190889ffd500d1260f6 |
completed | April 20, 2026, 12:04 p.m. |
Created at: April 16, 2026, 6:05 p.m.