Triple
T20778661
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gnostic Mass |
E511419
|
entity |
| Predicate | officiantRole |
P3343
|
FINISHED |
| Object | Priest |
—
|
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: Priest | Statement: [Gnostic Mass, officiantRole, Priest]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: officiantRole Context triple: [Gnostic Mass, officiantRole, Priest]
-
A.
liturgicalRole
Indicates the specific function or position an entity holds within a religious or liturgical context.
-
B.
ecclesiasticalRole
Indicates that one entity holds or is assigned a specific religious or church-related office, function, or position in relation to another entity.
-
C.
ceremonialRole
chosen
Indicates that an entity holds a formal, often symbolic or honorific, position or function within a ceremony or ritual context.
-
D.
ecclesialRole
Indicates that one entity holds or is assigned a specific role, office, or function within a church or ecclesiastical structure in relation to another entity.
-
E.
ceremonialRoleInvolves
Indicates that a ceremonial role includes or entails performing a particular action, duty, or function as part of that ceremony.
- 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_69e0b4cac7a48190a715cb3d545df2b4 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c26ed1a08190bb73824672328d98 |
completed | April 21, 2026, 12:18 a.m. |
| PD | Predicate disambiguation | batch_69e5c0550ec481908a0877fb2409d983 |
completed | April 20, 2026, 5:57 a.m. |
Created at: April 16, 2026, 12:37 p.m.