Triple
T9308896
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | sacrarium of Ops Consiva |
E223957
|
entity |
| Predicate | ritualSecrecy |
P87997
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [sacrarium of Ops Consiva, ritualSecrecy, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ritualSecrecy Context triple: [sacrarium of Ops Consiva, ritualSecrecy, yes]
-
A.
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.
-
B.
ritualCategory
Indicates the classification relationship that assigns a ritual to a specific ritual type or category.
-
C.
ritualCharacteristics
Indicates the defining features, practices, or attributes that characterize a particular ritual.
-
D.
relatedRitual
Indicates that one entity is associated with, connected to, or involved in the performance or context of a particular ritual.
-
E.
ritualPurpose
Indicates the intended function, goal, or role that a ritual is meant to serve or fulfill.
- 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_69ca8424d0f08190831e2e93c6533aeb |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd1daba67c819081d53545d67ef127 |
completed | April 1, 2026, 1:29 p.m. |
| PD | Predicate disambiguation | batch_69cc7a61e9a4819096eb014f3791ef2e |
completed | April 1, 2026, 1:52 a.m. |
| PDg | Predicate description generation | batch_69cc955a38108190b602d1e73725f11b |
completed | April 1, 2026, 3:47 a.m. |
Created at: March 30, 2026, 7:37 p.m.