Triple
T26153730
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mary Reeves |
E659898
|
entity |
| Predicate | managedPosthumousReleasesOf |
P167073
|
FINISHED |
| Object | Jim Reeves |
—
|
NE NERFINISHED |
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: Jim Reeves | Statement: [Mary Reeves, managedPosthumousReleasesOf, Jim Reeves]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: managedPosthumousReleasesOf Context triple: [Mary Reeves, managedPosthumousReleasesOf, Jim Reeves]
-
A.
hasPosthumousRelease
Indicates that a work was released or made publicly available only after its creator’s death.
-
B.
isPosthumousCollaboration
Indicates that a work results from a collaboration where at least one contributor was already deceased when the collaboration occurred or the work was completed.
-
C.
hasTributeReleasesFor
Indicates that one entity has released or produced tribute works (such as albums, songs, or performances) dedicated to another entity.
-
D.
isPosthumous
Indicates that something occurs, is created, or is conferred after the death of the person to whom it relates.
-
E.
releasedAfterDeathOf
Indicates that something (such as a work, product, or announcement) was released only after the death of a specified person.
- 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_69ee5bc5a9908190899d39ce95c6d215 |
completed | April 26, 2026, 6:39 p.m. |
| NER | Named-entity recognition | batch_69f6653ccf648190b65fb1141928e47e |
completed | May 2, 2026, 8:57 p.m. |
| PD | Predicate disambiguation | batch_69f6633451948190bcc0410602bb4914 |
completed | May 2, 2026, 8:48 p.m. |
| PDg | Predicate description generation | batch_69f663ff176c8190aaadb475f75daee4 |
completed | May 2, 2026, 8:52 p.m. |
Created at: April 26, 2026, 8:26 p.m.