Triple
T23714776
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | We Die Young (music video) |
E585966
|
entity |
| Predicate | featuresBandPerformance |
P48738
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [We Die Young (music video), featuresBandPerformance, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresBandPerformance Context triple: [We Die Young (music video), featuresBandPerformance, yes]
-
A.
livePerformanceFeature
chosen
Indicates that one entity is included or highlighted as a component of another entity’s live performance.
-
B.
featuresSoloPerformancesBy
Indicates that the subject includes or showcases solo performances carried out by the specified performer or performers.
-
C.
featuredSongPerformancesFrom
Indicates that certain song performances are highlighted or prominently presented as originating from a particular source, event, or context.
-
D.
musicOftenPerformedBy
Indicates that a particular piece of music, genre, or work is frequently performed or interpreted by a specific performer or group.
-
E.
performedInConcertBy
Indicates that an action, piece, or performance was carried out jointly by multiple participants as part of the same concert event.
- 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.