Triple
T35200049
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Will Caster |
E1016372
|
entity |
| Predicate | posthumousState |
P105054
|
FINISHED |
| Object | digitized consciousness |
—
|
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: digitized consciousness | Statement: [Will Caster, posthumousState, digitized consciousness]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: posthumousState Context triple: [Will Caster, posthumousState, digitized consciousness]
-
A.
posthumousLegalStatus
Indicates the legal condition or recognition assigned to a person or entity after their death.
-
B.
posthumousSuccess
Indicates that an entity achieves recognition, fame, or significant success only after its creator or originator has died.
-
C.
posthumousForm
chosen
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.
posthumousPresence
Indicates the continued influence, impact, or perceived presence of an entity after its death or cessation of 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_69f76dde814c8190a71f60d514a424a4 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78e344f18819088a4e5e75b2b69b7 |
completed | May 3, 2026, 6:04 p.m. |
| PD | Predicate disambiguation | batch_69f78b9106008190930b3b3675b737d6 |
completed | May 3, 2026, 5:53 p.m. |
Created at: May 3, 2026, 4:02 p.m.