Triple
T26108964
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lovin’ You for Life |
E658627
|
entity |
| Predicate | isPosthumousCollaboration |
P160340
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Lovin’ You for Life, isPosthumousCollaboration, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPosthumousCollaboration Context triple: [Lovin’ You for Life, isPosthumousCollaboration, true]
-
A.
isPosthumous
Indicates that something occurs, is created, or is conferred after the death of the person to whom it relates.
-
B.
hasPosthumousRelease
Indicates that a work was released or made publicly available only after its creator’s death.
-
C.
isPosthumousWorkOf
Indicates that a work was created, published, or became known only after the death of the person with whom it is associated.
-
D.
includesPosthumousPerformanceBy
Indicates that something (such as a work, recording, or release) contains or features a performance by an entity that was released or presented after that entity’s death.
-
E.
posthumousWorkUsedIn
Indicates that a work created or published after a creator’s death is utilized, referenced, or incorporated within another work or context.
- 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_69ee5bc20298819099a42be042eb2349 |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69f60779ae4c81909428c6d249cc0665 |
completed | May 2, 2026, 2:17 p.m. |
| PD | Predicate disambiguation | batch_69f5f7fd90fc81909055b211368f9139 |
completed | May 2, 2026, 1:11 p.m. |
| PDg | Predicate description generation | batch_69f600be0de88190989611e952b03117 |
completed | May 2, 2026, 1:48 p.m. |
Created at: April 26, 2026, 8 p.m.