Triple
T8764602
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Runnin (Deluxe bonus track) |
E208303
|
entity |
| Predicate | deluxeEditionStatus |
P53740
|
FINISHED |
| Object | deluxe bonus track |
—
|
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: deluxe bonus track | Statement: [Runnin (Deluxe bonus track), deluxeEditionStatus, deluxe bonus track]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: deluxeEditionStatus Context triple: [Runnin (Deluxe bonus track), deluxeEditionStatus, deluxe bonus track]
-
A.
hasDeluxeEdition
chosen
Indicates that an entity has an associated deluxe or enhanced edition version of itself.
-
B.
expandedEditionIncludes
Indicates that an expanded edition of a work contains, as part of its content, the material from another specified edition or version.
-
C.
hasDLC
Indicates that one entity includes, is associated with, or is supplemented by another entity as downloadable content.
-
D.
specialEdition
Indicates that an item is a distinct, limited, or enhanced version of a standard release, often with unique features, packaging, or content.
-
E.
containsAdditionalTracksBeyond
Indicates that one entity includes more tracks or items than are present in another referenced set or version.
- 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_69ca835df7e08190ac875664cca8f9ca |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5dfdef9881908a7f079d87e8e338 |
completed | March 31, 2026, 11:51 p.m. |
| PD | Predicate disambiguation | batch_69cc5c1884bc8190a46e8308db31f7ab |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:40 p.m.