Triple
T5896965
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apep |
E131122
|
entity |
| Predicate | ritualsAgainst |
P57110
|
FINISHED |
| Object | execration rituals |
—
|
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: execration rituals | Statement: [Apep, ritualsAgainst, execration rituals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ritualsAgainst Context triple: [Apep, ritualsAgainst, execration rituals]
-
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.
relatedRitual
chosen
Indicates that one entity is associated with, connected to, or involved in the performance or context of a particular ritual.
-
C.
ritualPurpose
Indicates the intended function, goal, or role that a ritual is meant to serve or fulfill.
-
D.
ritualAttitude
Indicates an entity’s characteristic stance, mindset, or emotional orientation toward a ritual or ritual practice.
-
E.
languageUsedInRituals
Indicates that a particular language is employed as the medium of speech, chant, or recitation during specific rituals or ceremonial practices.
- 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_69c00857439c819095950754176aa58a |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c0400f1af881908d376ea4793f6dea |
completed | March 22, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_69c0334dc8248190b7394dcece362d52 |
completed | March 22, 2026, 6:22 p.m. |
Created at: March 22, 2026, 3:58 p.m.