Triple
T23714673
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | We Die Young (EP) |
E585964
|
entity |
| Predicate | includesTrackLaterOnAlbum |
P143319
|
FINISHED |
| Object | We Die Young |
—
|
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: We Die Young | Statement: [We Die Young (EP), includesTrackLaterOnAlbum, We Die Young]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesTrackLaterOnAlbum Context triple: [We Die Young (EP), includesTrackLaterOnAlbum, We Die Young]
-
A.
precedesTrackOnAlbum
Indicates that one track appears immediately before another track in the ordering of tracks on the same album.
-
B.
containsAdditionalTracksBeyond
Indicates that one entity includes more tracks or items than are present in another referenced set or version.
-
C.
coveredOnAlbum
Indicates that a song or musical work has been recorded as a cover version and included on a particular album.
-
D.
followsInTracklist
Indicates that one item directly comes after another in an ordered tracklist sequence.
-
E.
trackIncluded
chosen
Indicates that a particular track is contained within, or forms part of, a larger collection, release, or grouping of tracks.
- 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_69e24905f77881908194d645676acd60 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b779f8508190a0a7f5496252b471 |
completed | April 29, 2026, 7:47 a.m. |
| PD | Predicate disambiguation | batch_69f155e4b1148190836ede4741dcb888 |
completed | April 29, 2026, 12:50 a.m. |
Created at: April 17, 2026, 6:54 p.m.