Triple
T32804784
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | D 957 |
E838992
|
entity |
| Predicate | isPosthumousCollection |
P175135
|
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: [D 957, isPosthumousCollection, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPosthumousCollection Context triple: [D 957, isPosthumousCollection, true]
-
A.
isPosthumous
Indicates that something occurs, is created, or is conferred after the death of the person to whom it relates.
-
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.
hasPosthumousRelease
Indicates that a work was released or made publicly available only after its creator’s death.
-
D.
isPosthumousWorkOf
Indicates that a work was created, published, or became known only after the death of the person with whom it is associated.
-
E.
managedPosthumousReleasesOf
Indicates that one entity oversaw, organized, or controlled the release of another entity’s works after that entity’s death.
- 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_69f3493d35208190b4351b4e85f2fa16 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6cee547108190ad3bc84297d8f516 |
completed | May 3, 2026, 4:28 a.m. |
| PD | Predicate disambiguation | batch_69f6cc1667a48190b42684f6ec22dae9 |
completed | May 3, 2026, 4:16 a.m. |
| PDg | Predicate description generation | batch_69f6ce6c76bc8190b865343d3f5810c9 |
completed | May 3, 2026, 4:26 a.m. |
Created at: May 1, 2026, 1:15 a.m.