Triple
T31315824
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Run (Taylor’s Version) (From the Vault) |
E798592
|
entity |
| Predicate | includedInDeluxeEdition |
P196437
|
FINISHED |
| Object | Red (Taylor’s Version) |
—
|
NE NERFINISHED |
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: Red (Taylor’s Version) | Statement: [Run (Taylor’s Version) (From the Vault), includedInDeluxeEdition, Red (Taylor’s Version)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includedInDeluxeEdition Context triple: [Run (Taylor’s Version) (From the Vault), includedInDeluxeEdition, Red (Taylor’s Version)]
-
A.
appearsOnDeluxeEdition
chosen
Indicates that an item (such as a track or feature) is included specifically on the deluxe edition of a work rather than (or in addition to) the standard edition.
-
B.
hasDeluxeEdition
Indicates that an entity has an associated deluxe or enhanced edition version of itself.
-
C.
hasDeluxeEditionTrackCount
Indicates the number of tracks included in the deluxe edition of a given release or work.
-
D.
includedInEdition
Indicates that one item (such as a work, text, or component) is contained within or forms part of a particular edition.
-
E.
hasDeluxeContent
Indicates that an entity includes or is associated with enhanced or premium content beyond the standard offering.
- 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_69f224e1932c81908fef14f7b03a10b7 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a011c64ff18819099195701bbecbb20 |
completed | May 11, 2026, 12:01 a.m. |
| PD | Predicate disambiguation | batch_6a011b7f7a508190b2ebb518fb7a2fe9 |
completed | May 10, 2026, 11:57 p.m. |
Created at: April 29, 2026, 9:15 p.m.