Triple
T20011669
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ghost of King Hamlet |
E494603
|
entity |
| Predicate | describesAfterlifeAs |
P23287
|
FINISHED |
| Object | purgatorial suffering |
—
|
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: purgatorial suffering | Statement: [Ghost of King Hamlet, describesAfterlifeAs, purgatorial suffering]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: describesAfterlifeAs Context triple: [Ghost of King Hamlet, describesAfterlifeAs, purgatorial suffering]
-
A.
afterlife
Indicates a relationship where an entity exists or experiences a state following physical death or the end of mortal life.
-
B.
associatedAfterlife
Indicates a relationship where an entity is linked to, or characterized by, a particular concept, realm, or state of existence after death.
-
C.
afterlifeFate
chosen
Indicates the outcome or condition an entity experiences in the afterlife as a result of its life or actions.
-
D.
afterlifeName
Indicates the name or designation assigned to an entity in an afterlife or post-mortem context.
-
E.
afterlifeForm
Indicates the form, state, or manifestation an entity takes in an afterlife or post-mortem existence.
- 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_69da626b2d748190886981ea90c8b2ea |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e6623773d88190826616a02d3c3e69 |
completed | April 20, 2026, 5:28 p.m. |
| PD | Predicate disambiguation | batch_69e54cdddbd48190becc8b2aa5ab4ef9 |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 3:34 p.m.