Triple
T2695055
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nephthys |
E58491
|
entity |
| Predicate | ritualRole |
P27714
|
FINISHED |
| Object | one of the two chief mourners for Osiris |
—
|
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: one of the two chief mourners for Osiris | Statement: [Nephthys, ritualRole, one of the two chief mourners for Osiris]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ritualRole Context triple: [Nephthys, ritualRole, one of the two chief mourners for Osiris]
-
A.
roleInRitual
chosen
Indicates the specific function, position, or responsibility an entity holds within a particular ritual or ceremonial activity.
-
B.
ritualSpecialist
Indicates that one entity serves as a designated expert or practitioner responsible for performing or overseeing rituals in relation to another entity or context.
-
C.
ritualCharacteristics
Indicates the defining features, practices, or attributes that characterize a particular ritual.
-
D.
ceremonialRole
Indicates that an entity holds a formal, often symbolic or honorific, position or function within a ceremony or ritual context.
-
E.
partOfRitual
Indicates that an action, object, or event is included as a component or step within a larger ritual.
- 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_69ab4ac269e481909cb317d79e68b75b |
completed | March 6, 2026, 9:44 p.m. |
| NER | Named-entity recognition | batch_69abda10a9bc81908473d02ab9116cef |
completed | March 7, 2026, 7:56 a.m. |
| PD | Predicate disambiguation | batch_69abd81ea5d88190ab5c8f8b8064b931 |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:55 p.m.