Triple
T23714700
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | We Die Young (EP) |
E585964
|
entity |
| Predicate | hasSubsequentAvailability |
P153673
|
FINISHED |
| Object | collector's item |
—
|
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: collector's item | Statement: [We Die Young (EP), hasSubsequentAvailability, collector's item]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSubsequentAvailability Context triple: [We Die Young (EP), hasSubsequentAvailability, collector's item]
-
A.
hasSubsequent
Indicates that one entity occurs, appears, or is positioned after another in a defined sequence or order.
-
B.
modernAvailability
Indicates that something is currently obtainable, accessible, or in use in the modern or present-day context.
-
C.
hasSubsequentWork
Indicates that one work is followed by another work that continues, succeeds, or builds upon it in sequence.
-
D.
hasSubsequentVersion
Indicates that one entity is a later or updated version that follows another entity in a version sequence.
-
E.
availabilityEnd
Indicates the point in time or condition after which something is no longer available or offered.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69f15b453da88190889a8d9b21727958 |
completed | April 29, 2026, 1:13 a.m. |
Created at: April 17, 2026, 6:54 p.m.