Triple
T35272552
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Don't Matter to Me |
E1018708
|
entity |
| Predicate | sideOfDoubleAlbum |
P25310
|
FINISHED |
| Object | B |
—
|
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: B | Statement: [Don't Matter to Me, sideOfDoubleAlbum, B]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sideOfDoubleAlbum Context triple: [Don't Matter to Me, sideOfDoubleAlbum, B]
-
A.
doubleAlbum
Indicates that a musical release is issued as a double album, typically spanning two discs or records as a single work.
-
B.
isDoubleAlbumTrack
Indicates that a track belongs to an album that was released as a double album (i.e., spanning two discs or equivalent units).
-
C.
onAlbumSide
chosen
Indicates that a particular track or song appears on a specified side (e.g., Side A or Side B) of an album.
-
D.
isDoubleSong
Indicates that one song is a duplicate or alternate version of another song, such as a second take, remix, or re-recording.
-
E.
isDoubleCoverOf
Indicates that one object serves as a two-to-one covering of another, such that each point or element of the second is covered by exactly two corresponding points or elements of the first.
- 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_69f76de5c4788190896ad598ae7d6bc6 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78fa095ec81908c609d9a6c63363b |
completed | May 3, 2026, 6:10 p.m. |
| PD | Predicate disambiguation | batch_69f78e2f52e08190a77661223a96c601 |
completed | May 3, 2026, 6:04 p.m. |
Created at: May 3, 2026, 4:02 p.m.