Triple
T18645773
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pearl |
E455800
|
entity |
| Predicate | reasonForPosthumousRelease |
P70267
|
FINISHED |
| Object | released after Janis Joplin’s death in 1970 |
—
|
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: released after Janis Joplin’s death in 1970 | Statement: [Pearl, reasonForPosthumousRelease, released after Janis Joplin’s death in 1970]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reasonForPosthumousRelease Context triple: [Pearl, reasonForPosthumousRelease, released after Janis Joplin’s death in 1970]
-
A.
reasonForRelease
Indicates the cause, justification, or circumstance that led to an entity being released.
-
B.
hasPosthumousRelease
Indicates that a work was released or made publicly available only after its creator’s death.
-
C.
releasedAfterDeathOf
chosen
Indicates that something (such as a work, product, or announcement) was released only after the death of a specified person.
-
D.
laterReReleasedBy
Indicates that an entity was re-released at a later time by a specified agent or organization.
-
E.
posthumousPublicationDate
Indicates the date on which a work was first published after its creator’s death.
- 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_69d8d38ea1e88190997e9b231190ba6f |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e5500d69648190800da65de0c191b8 |
completed | April 19, 2026, 9:58 p.m. |
| PD | Predicate disambiguation | batch_69e478d85864819093cbad5ed9b54878 |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:47 a.m.