Triple
T27149423
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | St Peter's Church, Prestbury |
E682343
|
entity |
| Predicate | hasDiocesanBishopSee |
P104560
|
FINISHED |
| Object | Chester |
—
|
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: Chester | Statement: [St Peter's Church, Prestbury, hasDiocesanBishopSee, Chester]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDiocesanBishopSee Context triple: [St Peter's Church, Prestbury, hasDiocesanBishopSee, Chester]
-
A.
hasDiocesanSee
chosen
Indicates that a bishop or ecclesiastical jurisdiction holds its official diocesan seat or central cathedral in a particular location.
-
B.
hasDiocesanBishops
Indicates that a church, diocese, or ecclesiastical jurisdiction is served or overseen by one or more diocesan bishops.
-
C.
hasApostolicSee
Indicates that a religious jurisdiction or entity is under the authority or oversight of a particular apostolic see (central episcopal seat).
-
D.
dioceseBishop
Indicates that a person serves as the bishop (ecclesiastical leader) of a specified diocese.
-
E.
isDiocesanSeatOf
Indicates that a location serves as the central administrative seat or headquarters 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_69eefaceb2a08190b9659b7f730629f5 |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69f7626667f48190ad90867eb67ec582 |
completed | May 3, 2026, 2:57 p.m. |
| PD | Predicate disambiguation | batch_69f76175d6608190b60b268e20f49ed9 |
completed | May 3, 2026, 2:53 p.m. |
Created at: April 27, 2026, 9:13 a.m.