Triple
T21633092
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Book with No Pictures |
E533881
|
entity |
| Predicate | coverDesign |
P145323
|
FINISHED |
| Object | minimalist text-based cover |
—
|
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 text-based cover | Statement: [The Book with No Pictures, coverDesign, minimalist text-based cover]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coverDesign Context triple: [The Book with No Pictures, coverDesign, minimalist text-based cover]
-
A.
cover
Indicates that one entity extends over, conceals, protects, or provides a surface or layer for another entity.
-
B.
coverText
Indicates that one text serves as the cover or front-facing textual representation for another work or resource.
-
C.
coverDesignationFor
Indicates that one entity serves as the designated cover or protective layer for another entity.
-
D.
coverMedium
Indicates that one entity serves as the physical or digital medium on which another entity (typically a cover or cover art) is realized or presented.
-
E.
coverInker
Indicates that one entity is responsible for inking over the cover artwork created by another entity.
- 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_69e0c465ae7481908577b7209fdb2a77 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ef52185dbc819096ad2fc5b7d953f8 |
completed | April 27, 2026, 12:10 p.m. |
| PD | Predicate disambiguation | batch_69e69677b9c48190bf81f795aa8ad74e |
completed | April 20, 2026, 9:11 p.m. |
| PDg | Predicate description generation | batch_69e69cb4bcbc8190a4fc2d508df107be |
completed | April 20, 2026, 9:37 p.m. |
Created at: April 16, 2026, 6:35 p.m.