Triple
T18867408
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lord of the Sacred Land |
E461474
|
entity |
| Predicate | associatedRitualContext |
P57110
|
FINISHED |
| Object | mummification |
—
|
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: mummification | Statement: [Lord of the Sacred Land, associatedRitualContext, mummification]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedRitualContext Context triple: [Lord of the Sacred Land, associatedRitualContext, mummification]
-
A.
relatedRitual
chosen
Indicates that one entity is associated with, connected to, or involved in the performance or context of a particular ritual.
-
B.
mentionsRitual
Indicates that one entity refers to, discusses, or otherwise makes mention of a ritual associated with another entity.
-
C.
appearsInRitual
Indicates that an entity is included, featured, or participates as a component or element within a specific ritual.
-
D.
hasRitualContext
Indicates that one entity is associated with, or occurs within, a ritual or ceremonial context in relation to another entity.
-
E.
ritualCategory
Indicates the classification relationship that assigns a ritual to a specific ritual type or category.
- 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_69d8dcfb7b9c8190854e7b171b98ea2e |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5c2a6d1d081909b6dab2a5166a317 |
completed | April 20, 2026, 6:07 a.m. |
| PD | Predicate disambiguation | batch_69e48d2166b88190add38de96cedc65c |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:57 a.m.