Triple
T10326980
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Senusret I |
E242783
|
entity |
| Predicate | cultAfterDeath |
P48829
|
FINISHED |
| Object | venerated as a deified king |
—
|
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: venerated as a deified king | Statement: [Senusret I, cultAfterDeath, venerated as a deified king]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cultAfterDeath Context triple: [Senusret I, cultAfterDeath, venerated as a deified king]
-
A.
associatedAfterlife
chosen
Indicates a relationship where an entity is linked to, or characterized by, a particular concept, realm, or state of existence after death.
-
B.
afterDeath
Indicates that one event, state, or condition occurs subsequent to and as a result of an entity’s death.
-
C.
residenceAfterDeath
Indicates the location where an individual is said to reside or be located after their death.
-
D.
releasedAfterDeathOf
Indicates that something (such as a work, product, or announcement) was released only after the death of a specified person.
-
E.
afterlifeFate
Indicates the outcome or condition an entity experiences in the afterlife as a result of its life or actions.
- 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_69d381af787481908bc401325c760a88 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4d7ce69b881909f27d97c90643634 |
completed | April 7, 2026, 10:09 a.m. |
| PD | Predicate disambiguation | batch_69d4d1f64a648190a79980d647898eb0 |
completed | April 7, 2026, 9:44 a.m. |
Created at: April 6, 2026, 11:51 a.m.