Triple
T9424983
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lovesexy |
E227242
|
entity |
| Predicate | hasSuiteLikeCDMastering |
P88812
|
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: [Lovesexy, hasSuiteLikeCDMastering, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSuiteLikeCDMastering Context triple: [Lovesexy, hasSuiteLikeCDMastering, true]
-
A.
hasRemastering
Indicates that one version of a work is a remastered form derived from another version of the same work.
-
B.
isMultiPlatinum
Indicates that an entity (typically a music recording or artist) has achieved multiple platinum-level sales or certification thresholds.
-
C.
recordLabelEligibility
Indicates that an entity meets the criteria or conditions required to be eligible for association with a particular record label.
-
D.
isDoubleAlbumTrack
Indicates that a track belongs to an album that was released as a double album (i.e., spanning two discs or equivalent units).
-
E.
hasOrchestralSuite
Indicates that a musical work is associated with, or has been arranged into, an orchestral suite derived from it.
- 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_69ca8436ba308190903e470776d2d893 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd7c8f59dc8190854dfc0d287731c6 |
completed | April 1, 2026, 8:14 p.m. |
| PD | Predicate disambiguation | batch_69cca550777c819094e1851a6127cbbc |
completed | April 1, 2026, 4:55 a.m. |
| PDg | Predicate description generation | batch_69cca89b3368819087a3d69270c1f185 |
completed | April 1, 2026, 5:09 a.m. |
Created at: March 30, 2026, 7:49 p.m.