Triple
T5992262
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maat |
E133376
|
entity |
| Predicate | functionInAfterlife |
P48829
|
FINISHED |
| Object | standard for judgment of the dead |
—
|
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: standard for judgment of the dead | Statement: [Maat, functionInAfterlife, standard for judgment of the dead]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: functionInAfterlife Context triple: [Maat, functionInAfterlife, standard for judgment of the dead]
-
A.
afterlifeFate
Indicates the outcome or condition an entity experiences in the afterlife as a result of its life or actions.
-
B.
associatedAfterlife
chosen
Indicates a relationship where an entity is linked to, or characterized by, a particular concept, realm, or state of existence after death.
-
C.
afterlifeForm
Indicates the form, state, or manifestation an entity takes in an afterlife or post-mortem existence.
-
D.
functionInWork
Indicates that a particular function, role, or operation is performed, utilized, or occurs within the context of a specific work or creation.
-
E.
formerFunction
Indicates that an entity previously held a specific role, position, or function but no longer does so.
- 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_69c0087010d081908bb8142342d63330 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c04e8fd030819095a4f3b3d425ec21 |
completed | March 22, 2026, 8:18 p.m. |
| PD | Predicate disambiguation | batch_69c049e152e88190979ab80cb9b50321 |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:05 p.m.