Triple
T22165262
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Eternal Idol |
E547772
|
entity |
| Predicate | deluxeEditionIncludes |
P60752
|
FINISHED |
| Object | bonus tracks |
—
|
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: bonus tracks | Statement: [The Eternal Idol, deluxeEditionIncludes, bonus tracks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: deluxeEditionIncludes Context triple: [The Eternal Idol, deluxeEditionIncludes, bonus tracks]
-
A.
expandedEditionIncludes
chosen
Indicates that an expanded edition of a work contains, as part of its content, the material from another specified edition or version.
-
B.
deluxeEditionReleaseDate
Indicates the date on which a deluxe edition of a work is officially released.
-
C.
hasDeluxeEdition
Indicates that an entity has an associated deluxe or enhanced edition version of itself.
-
D.
containsAdditionalTracksBeyond
Indicates that one entity includes more tracks or items than are present in another referenced set or version.
-
E.
specialEdition
Indicates that an item is a distinct, limited, or enhanced version of a standard release, often with unique features, packaging, or content.
- 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_69e11e3c4c5c81908d336165816b12e0 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f12a314cc081908857c13d018d52b2 |
completed | April 28, 2026, 9:44 p.m. |
| PD | Predicate disambiguation | batch_69e71b41555881909b8e22718974d527 |
completed | April 21, 2026, 6:37 a.m. |
Created at: April 16, 2026, 8:34 p.m.