Triple
T23552198
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Above (Deluxe Edition) |
E578082
|
entity |
| Predicate | hasBonusContentType |
P147622
|
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: [Above (Deluxe Edition), hasBonusContentType, bonus tracks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBonusContentType Context triple: [Above (Deluxe Edition), hasBonusContentType, bonus tracks]
-
A.
hasBonusMaterial
chosen
Indicates that an item includes additional supplementary content beyond its main or primary material.
-
B.
hasBonusTrackStatus
Indicates whether an item (such as a track or release) is designated as a bonus track in relation to a primary work or edition.
-
C.
hasContentType
Indicates that an entity is associated with or classified by a specific type of content.
-
D.
hasBenefitType
Indicates that an entity is associated with a specific category or type of benefit it provides or receives.
-
E.
hasWonBonus
Indicates that an entity has received or been awarded a bonus, typically as a result of meeting certain conditions or achieving specific performance.
- 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_69e245fa93448190919cb04534560542 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f1aecf28508190b8d3396591e5e6bb |
completed | April 29, 2026, 7:10 a.m. |
| PD | Predicate disambiguation | batch_69f118afabd88190bd88f49597d120e8 |
completed | April 28, 2026, 8:29 p.m. |
Created at: April 17, 2026, 6:11 p.m.