Triple
T21721990
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | All My Life |
E536180
|
entity |
| Predicate | isFromSoundtrackAlbum |
P46647
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [All My Life, isFromSoundtrackAlbum, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isFromSoundtrackAlbum Context triple: [All My Life, isFromSoundtrackAlbum, true]
-
A.
isOnSoundtrack
chosen
Indicates that a piece of music is included as part of the official soundtrack for a particular work (such as a film, game, or show).
-
B.
isSoundtrackOf
Indicates that a piece of music or collection of music serves as the soundtrack for a particular work, such as a film, game, or show.
-
C.
hasSoundtrackCharacteristic
Indicates that a soundtrack possesses a specified quality, feature, or attribute.
-
D.
hasSoundtrackWork
Indicates that one entity (typically a media product or work) includes or is associated with another entity that serves as its soundtrack or musical score.
-
E.
followsInFilmSoundtrack
Indicates that one musical piece in a film’s soundtrack comes immediately after another in the sequence or ordering of the soundtrack.
- 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_69e0c46c6dd88190a595375fa6ebd701 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69efd97032c08190820b87a288e77293 |
completed | April 27, 2026, 9:47 p.m. |
| PD | Predicate disambiguation | batch_69e6969725bc81908e7ad19619ba2688 |
completed | April 20, 2026, 9:11 p.m. |
Created at: April 16, 2026, 6:47 p.m.