Triple
T12905631
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Big Shot |
E308721
|
entity |
| Predicate | hasCoverArtFormat |
P10512
|
FINISHED |
| Object | 7-inch single sleeve |
—
|
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: 7-inch single sleeve | Statement: [Big Shot, hasCoverArtFormat, 7-inch single sleeve]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCoverArtFormat Context triple: [Big Shot, hasCoverArtFormat, 7-inch single sleeve]
-
A.
hasCoverArtSource
Indicates that an entity’s cover art is derived from, or visually based on, another specified source entity.
-
B.
hasCoverArtVariant
Indicates that an item has an alternative version of its cover artwork distinct from the primary cover.
-
C.
hasCoverArtTheme
Indicates that an item’s cover art visually represents or is characterized by a particular theme or motif.
-
D.
hasCoverArtFeaturing
Indicates that one entity’s cover art visually features or depicts another entity.
-
E.
hasCoverType
chosen
Indicates that one entity possesses or is associated with a specific type or category of cover.
- 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_69d7bdf92b588190acdf2a2291ac4590 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d971831bd48190b0ecd13e7181bbc6 |
completed | April 10, 2026, 9:54 p.m. |
| PD | Predicate disambiguation | batch_69d96fa9b7708190a9e9fa30f59ff580 |
completed | April 10, 2026, 9:46 p.m. |
Created at: April 9, 2026, 5:41 p.m.