Triple
T7604923
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Archdeaconry of Ludlow |
E180077
|
entity |
| Predicate | hasClericalRankInCharge |
P3655
|
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 Ludlow, hasClericalRankInCharge, archdeacon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasClericalRankInCharge Context triple: [Archdeaconry of Ludlow, hasClericalRankInCharge, archdeacon]
-
A.
hasClericalFunction
Indicates that an entity performs, is responsible for, or is associated with a clerical or administrative function.
-
B.
hasLiturgicalRank
chosen
Indicates that an entity is assigned a specific status or level within a liturgical or religious ceremonial hierarchy.
-
C.
isClericIn
Indicates that an entity serves or functions as a cleric within a specified organization, location, or group.
-
D.
hasClergyOrder
Indicates that an entity is associated with, or belongs to, a specific religious or clerical order.
-
E.
hasClericalDiscipline
Indicates that an entity is subject to, or governed by, a particular set of clerical or religious disciplinary rules or practices.
- 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_69c69f3567008190ab01d2ca7b53584a |
completed | March 27, 2026, 3:16 p.m. |
| NER | Named-entity recognition | batch_69c6f9fbd1408190b721bf016f997c7b |
completed | March 27, 2026, 9:43 p.m. |
| PD | Predicate disambiguation | batch_69c6f4e485f88190910b39da52a955fe |
completed | March 27, 2026, 9:21 p.m. |
Created at: March 27, 2026, 3:54 p.m.