Triple
T24096142
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Archdeacons of the Diocese of Worcester |
E596923
|
entity |
| Predicate | isClericalRankAbove |
P84087
|
FINISHED |
| Object | incumbent |
—
|
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: incumbent | Statement: [Archdeacons of the Diocese of Worcester, isClericalRankAbove, incumbent]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isClericalRankAbove Context triple: [Archdeacons of the Diocese of Worcester, isClericalRankAbove, incumbent]
-
A.
hasLiturgicalRank
Indicates that an entity is assigned a specific status or level within a liturgical or religious ceremonial hierarchy.
-
B.
isClericIn
Indicates that an entity serves or functions as a cleric within a specified organization, location, or group.
-
C.
isCleric
Indicates that an entity holds the role or status of a cleric, typically serving a religious or spiritual function.
-
D.
hasClericalFunction
Indicates that an entity performs, is responsible for, or is associated with a clerical or administrative function.
-
E.
isAboveOfficerGrade
chosen
Indicates that one entity holds a rank or position higher than an officer-grade level relative to 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_69e288c548048190a5c1018da1166a21 |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1dd24ad9c8190ae81bcc5eae6e159 |
completed | April 29, 2026, 10:27 a.m. |
| PD | Predicate disambiguation | batch_69f17651458c8190bbfd301883e46085 |
completed | April 29, 2026, 3:09 a.m. |
Created at: April 17, 2026, 10:58 p.m.