Triple
T15939476
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pound Cake / Paris Morton Music 2 |
E386520
|
entity |
| Predicate | isDoubleSong |
P121064
|
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: [Pound Cake / Paris Morton Music 2, isDoubleSong, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isDoubleSong Context triple: [Pound Cake / Paris Morton Music 2, isDoubleSong, true]
-
A.
isDoubleAlbumTrack
Indicates that a track belongs to an album that was released as a double album (i.e., spanning two discs or equivalent units).
-
B.
hasVocalDuet
Indicates that two entities perform or participate together in a vocal duet.
-
C.
hasTwoTracks
Indicates that the subject possesses or is associated with exactly two distinct tracks or pathways.
-
D.
doubleAlbum
Indicates that a musical release is issued as a double album, typically spanning two discs or records as a single work.
-
E.
isDoubleAAsideWith
Indicates that two entities are paired together as a double A-side, typically sharing equal prominence in a joint release (such as two lead tracks on the same single).
- F. None of above. chosen
Provenance (4 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_69d86da750008190987eb26be3f6c118 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e17d4d08f481909f38b75e3f42d9ab |
completed | April 17, 2026, 12:22 a.m. |
| PD | Predicate disambiguation | batch_69e142d37cd88190ab50760f1783e20c |
completed | April 16, 2026, 8:13 p.m. |
| PDg | Predicate description generation | batch_69e17d48cc9c8190b03fd07ae2e9dfd8 |
completed | April 17, 2026, 12:22 a.m. |
Created at: April 10, 2026, 4:53 a.m.