Triple
T19416459
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Archdeaconry of Manchester |
E485728
|
entity |
| Predicate | clergyTitleInCharge |
P54251
|
FINISHED |
| Object | Archdeacon |
—
|
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: Archdeacon | Statement: [Archdeaconry of Manchester, clergyTitleInCharge, Archdeacon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: clergyTitleInCharge Context triple: [Archdeaconry of Manchester, clergyTitleInCharge, Archdeacon]
-
A.
clergySystem
Indicates a relationship in which an organized religious institution or tradition has a structured system of clergy roles, ranks, or offices.
-
B.
ecclesiasticalRole
chosen
Indicates that one entity holds or is assigned a specific religious or church-related office, function, or position in relation to another entity.
-
C.
clergymanTo
Indicates a relationship where one entity serves as or acts in the role of a clergyman in relation to another entity.
-
D.
clergy
Indicates that an entity serves in an official religious or spiritual leadership role within an organized faith or religious institution.
-
E.
clergyCan
Indicates that members of the clergy are permitted or authorized to perform a specified action or exercise a particular role or function.
- 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_69d8e8d688f881909c85104a62e09d8a |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e62af9c8fc81909860de10b6720207 |
completed | April 20, 2026, 1:32 p.m. |
| PD | Predicate disambiguation | batch_69e4fd68b1f881908d273de1fee81a75 |
completed | April 19, 2026, 4:06 p.m. |
Created at: April 10, 2026, 1:37 p.m.