Triple
T20623148
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Die, Die My Darling |
E506750
|
entity |
| Predicate | hasKeyReissue |
P140814
|
FINISHED |
| Object | Misfits compilation releases |
—
|
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: Misfits compilation releases | Statement: [Die, Die My Darling, hasKeyReissue, Misfits compilation releases]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasKeyReissue Context triple: [Die, Die My Darling, hasKeyReissue, Misfits compilation releases]
-
A.
hasKeyIssue
Indicates that an entity is associated with a primary or central problem, concern, or topic of importance.
-
B.
hasSubsequentReissue
Indicates that one entity is a later reissued version that follows another entity in sequence.
-
C.
hasReissueHistory
Indicates that an entity has a record of being reissued or having undergone one or more reissue events in its history.
-
D.
hasReissuePeriod
Indicates the time span during which something (such as a document, license, or product) may be reissued or renewed.
-
E.
hasReissueProgram
Indicates that an entity offers a program or process for issuing replacements or updated versions of something previously provided.
- 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_69e0b4bc90988190ac360aaf645efc1d |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6abe3177c8190ad1b2ca8b1e0a560 |
completed | April 20, 2026, 10:42 p.m. |
| PD | Predicate disambiguation | batch_69e5a00c43308190b7ea58d559257e07 |
completed | April 20, 2026, 3:39 a.m. |
| PDg | Predicate description generation | batch_69e5a6a9f3f88190b961db9aca36f7da |
completed | April 20, 2026, 4:08 a.m. |
Created at: April 16, 2026, 11:42 a.m.