Triple
T5428292
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dean of Worcester |
E121418
|
entity |
| Predicate | isClericalRank |
P5046
|
FINISHED |
| Object | senior 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: senior priest | Statement: [Dean of Worcester, isClericalRank, senior priest]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isClericalRank Context triple: [Dean of Worcester, isClericalRank, senior priest]
-
A.
hasLiturgicalRank
Indicates that an entity is assigned a specific status or level within a liturgical or religious ceremonial hierarchy.
-
B.
hasClericalFunction
Indicates that an entity performs, is responsible for, or is associated with a clerical or administrative function.
-
C.
hasClergyType
Indicates the specific category or role of clergy associated with an entity.
-
D.
ecclesiasticalRank
chosen
Indicates the hierarchical religious office or clerical status that one entity holds within a church or ecclesiastical organization.
-
E.
isClericalBodyFor
Indicates that one entity functions as the official clerical or administrative body responsible for serving, supporting, or governing another entity.
- 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_69bd463c65f0819082ee6483ab4b466a |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd8911a7348190ad9378a248190f07 |
completed | March 20, 2026, 5:51 p.m. |
| PD | Predicate disambiguation | batch_69bd846b8bdc81909dcdc2a3084226f2 |
completed | March 20, 2026, 5:31 p.m. |
Created at: March 20, 2026, 2:06 p.m.