Triple
T24538554
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Canterbury Cathedral choir |
E607023
|
entity |
| Predicate | homeDiocese |
P2740
|
FINISHED |
| Object | Diocese of Canterbury |
—
|
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 Canterbury | Statement: [Canterbury Cathedral choir, homeDiocese, Diocese of Canterbury]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homeDiocese Context triple: [Canterbury Cathedral choir, homeDiocese, Diocese of Canterbury]
-
A.
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.
-
B.
administrativeDiocese
Indicates that one entity serves as the ecclesiastical administrative diocese responsible for the governance or oversight of another entity.
-
C.
diocesanUse
Indicates that something is used, practiced, or applied within the authority, jurisdiction, or customary practice of a particular diocese.
-
D.
dioceseBishop
Indicates that a person serves as the bishop (ecclesiastical leader) of a specified diocese.
-
E.
dioceseLater
Indicates that one diocese exists or is established later in time than another 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_69e2c4c9bf94819082d05da6f5c29907 |
completed | April 17, 2026, 11:39 p.m. |
| NER | Named-entity recognition | batch_69f2be044d4c819094e14eda28d371a7 |
completed | April 30, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69f2a6b0ca8081908d931aec560eae56 |
completed | April 30, 2026, 12:47 a.m. |
Created at: April 18, 2026, 2:26 a.m.