Triple
T32446649
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Augustinian Canons monastery |
E829165
|
entity |
| Predicate | liturgyRole |
P11534
|
FINISHED |
| Object | cathedral clergy |
—
|
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: cathedral clergy | Statement: [Augustinian Canons monastery, liturgyRole, cathedral clergy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: liturgyRole Context triple: [Augustinian Canons monastery, liturgyRole, cathedral clergy]
-
A.
liturgicalRole
chosen
Indicates the specific function or position an entity holds within a religious or liturgical context.
-
B.
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.
-
C.
ecclesiasticalRole
Indicates that one entity holds or is assigned a specific religious or church-related office, function, or position in relation to another entity.
-
D.
positionOnLiturgy
Indicates the stance or viewpoint an entity holds regarding liturgical practices, forms, or regulations.
-
E.
liturgicalCharacter
Indicates the specific role, function, or significance that something holds within a liturgical or worship context.
- 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_69f3491d2e5c819092b1c9535beff8ec |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c2e66478819086a588340ec05a53 |
completed | May 3, 2026, 3:37 a.m. |
| PD | Predicate disambiguation | batch_69f6bd25bed08190befcabd3a41ffadf |
completed | May 3, 2026, 3:12 a.m. |
Created at: May 1, 2026, 12:56 a.m.