Triple
T25415525
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Passionate Witch |
E636821
|
entity |
| Predicate | completedPosthumously |
P4225
|
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: [The Passionate Witch, completedPosthumously, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: completedPosthumously Context triple: [The Passionate Witch, completedPosthumously, true]
-
A.
isPosthumous
chosen
Indicates that something occurs, is created, or is conferred after the death of the person to whom it relates.
-
B.
posthumousWorkUsedIn
Indicates that a work created or published after a creator’s death is utilized, referenced, or incorporated within another work or context.
-
C.
posthumousForm
Indicates a form, version, or representation of something that is created, recognized, or exists only after the death of the associated entity.
-
D.
posthumousAction
Indicates an action or event that occurs or is carried out after the death of the person to whom it relates.
-
E.
posthumousSuccess
Indicates that an entity achieves recognition, fame, or significant success only after its creator or originator has died.
- 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_69e75db4135881909acc287ebcb7a505 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5b0119ee0819088c4985bd7862cab |
completed | May 2, 2026, 8:04 a.m. |
| PD | Predicate disambiguation | batch_69f49377411c8190b2188de444d76795 |
completed | May 1, 2026, 11:50 a.m. |
Created at: April 21, 2026, 1:55 p.m.