Triple
T17987169
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hardcore Will Never Die, But You Will |
E430264
|
entity |
| Predicate | bonusTrackOn |
P85255
|
FINISHED |
| Object | special edition |
—
|
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: special edition | Statement: [Hardcore Will Never Die, But You Will, bonusTrackOn, special edition]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bonusTrackOn Context triple: [Hardcore Will Never Die, But You Will, bonusTrackOn, special edition]
-
A.
hasBonusTrackStatus
chosen
Indicates whether an item (such as a track or release) is designated as a bonus track in relation to a primary work or edition.
-
B.
trackOn
Indicates that one entity is physically positioned or moving along the surface or path of another, like a vehicle on a track or rails.
-
C.
isNewTrackOn
Indicates that a track has just started playing or has recently become the current active track.
-
D.
containsAdditionalTracksBeyond
Indicates that one entity includes more tracks or items than are present in another referenced set or version.
-
E.
nonAlbumTrack
Indicates that a track is not part of any official album release.
- 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_69d8b90364248190a37381adea932f42 |
completed | April 10, 2026, 8:46 a.m. |
| NER | Named-entity recognition | batch_69e4b29c6d0881909d450d2561d532a6 |
completed | April 19, 2026, 10:46 a.m. |
| PD | Predicate disambiguation | batch_69e3f90039e4819080527f860dca042e |
completed | April 18, 2026, 9:34 p.m. |
Created at: April 10, 2026, 10:23 a.m.