Triple
T21703016
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bishop of Knaresborough |
E535700
|
entity |
| Predicate | withinDiocese |
P2740
|
FINISHED |
| Object | Diocese of Ripon |
—
|
NE NERFINISHED |
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: Diocese of Ripon | Statement: [Bishop of Knaresborough, withinDiocese, Diocese of Ripon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: withinDiocese Context triple: [Bishop of Knaresborough, withinDiocese, Diocese of Ripon]
-
A.
operatesWithinDiocese
Indicates that an entity carries out its functions or activities under the jurisdiction of a specified diocese.
-
B.
administrativeDiocese
Indicates that one entity serves as the ecclesiastical administrative diocese responsible for the governance or oversight of another entity.
-
C.
diocese
chosen
Indicates that one entity serves as the ecclesiastical district or jurisdiction under the authority of a bishop to which the other entity is related or belongs.
-
D.
linkedDiocese
Indicates a formal association or connection established between one diocese and another.
-
E.
diocesanUse
Indicates that something is used, practiced, or applied within the authority, jurisdiction, or customary practice of a particular diocese.
- 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_69e0c46b44c0819088ab883ebd44e0e8 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ef9b8161348190842c433531cfaa5b |
completed | April 27, 2026, 5:23 p.m. |
| PD | Predicate disambiguation | batch_69e6969113cc8190ab69855ef5667e4b |
completed | April 20, 2026, 9:11 p.m. |
Created at: April 16, 2026, 6:46 p.m.