Triple
T22679909
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apepi |
E560449
|
entity |
| Predicate | ritualsDirectedAt |
P149215
|
FINISHED |
| Object | protective rituals against him |
—
|
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: protective rituals against him | Statement: [Apepi, ritualsDirectedAt, protective rituals against him]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ritualsDirectedAt Context triple: [Apepi, ritualsDirectedAt, protective rituals against him]
-
A.
ritualActivities
Indicates that one entity engages in, performs, or is associated with ritualistic or ceremonial activities in relation to another entity or context.
-
B.
ritualCategory
Indicates the classification relationship that assigns a ritual to a specific ritual type or category.
-
C.
ritualPurpose
Indicates the intended function, goal, or role that a ritual is meant to serve or fulfill.
-
D.
ritualSignificance
Indicates that something holds special importance or meaning within a ritual or ceremonial context.
-
E.
ritualEvent
Indicates that an event is a ritual or ceremonial occurrence, typically involving prescribed actions, symbols, or practices performed according to tradition or custom.
- F. None of above. chosen
Provenance (4 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_69e2454bfd00819099115715a22cb057 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f1785f68b4819082c5570f741f5135 |
completed | April 29, 2026, 3:17 a.m. |
| PD | Predicate disambiguation | batch_69ee62a6245881909506ff502da14137 |
completed | April 26, 2026, 7:08 p.m. |
| PDg | Predicate description generation | batch_69ee8843d3308190b6e22bb98ae5c3d8 |
completed | April 26, 2026, 9:48 p.m. |
Created at: April 17, 2026, 3:11 p.m.