Triple
T24634312
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Love Will Tear Us Apart |
E609761
|
entity |
| Predicate | posthumousReleaseRelativeTo |
P70267
|
FINISHED |
| Object | death of Ian Curtis |
—
|
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: death of Ian Curtis | Statement: [Love Will Tear Us Apart, posthumousReleaseRelativeTo, death of Ian Curtis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: posthumousReleaseRelativeTo Context triple: [Love Will Tear Us Apart, posthumousReleaseRelativeTo, death of Ian Curtis]
-
A.
posthumousPublicationDate
Indicates the date on which a work was first published after its creator’s death.
-
B.
hasPosthumousRelease
Indicates that a work was released or made publicly available only after its creator’s death.
-
C.
isPosthumous
Indicates that something occurs, is created, or is conferred after the death of the person to whom it relates.
-
D.
releasedAfterDeathOf
chosen
Indicates that something (such as a work, product, or announcement) was released only after the death of a specified person.
-
E.
posthumousForm
Indicates a form, version, or representation of something that is created, recognized, or exists only after the death of the associated entity.
- 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_69e2c4d28f848190ac38c400060e943d |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f2be064ff88190b5d9e5ec75a41242 |
completed | April 30, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69f2a6d0ab708190b2e3b94dd20ca76b |
completed | April 30, 2026, 12:48 a.m. |
Created at: April 18, 2026, 2:32 a.m.