Triple
T28523040
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The White Album |
E721837
|
entity |
| Predicate | hasCoverDesign |
P1529
|
FINISHED |
| Object | minimalist white cover in many editions |
—
|
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: minimalist white cover in many editions | Statement: [The White Album, hasCoverDesign, minimalist white cover in many editions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCoverDesign Context triple: [The White Album, hasCoverDesign, minimalist white cover in many editions]
-
A.
coverDesign
Indicates that one entity is responsible for creating or specifying the visual design of another entity’s cover (such as a book, album, or publication).
-
B.
hasCoverType
Indicates that one entity possesses or is associated with a specific type or category of cover.
-
C.
isCover
Indicates that one entity functions as a protective or concealing layer over another entity.
-
D.
containsCoverOf
Indicates that one entity includes within it a cover or covering representation of another entity.
-
E.
hasDesign
chosen
Indicates that one entity possesses, embodies, or is characterized by a particular design associated with 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_69f01a5cbcc4819083fb4e723378713e |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69ffb82be8148190a1c870d467a28c80 |
completed | May 9, 2026, 10:41 p.m. |
| PD | Predicate disambiguation | batch_69ffb7bbd550819094052e9a0d0ae320 |
completed | May 9, 2026, 10:39 p.m. |
Created at: April 28, 2026, 3:22 a.m.