Triple
T25727115
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bishop of Willochra |
E645139
|
entity |
| Predicate | typeOfDioceseLed |
P89989
|
FINISHED |
| Object | rural Anglican diocese |
—
|
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: rural Anglican diocese | Statement: [Bishop of Willochra, typeOfDioceseLed, rural Anglican diocese]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfDioceseLed Context triple: [Bishop of Willochra, typeOfDioceseLed, rural Anglican diocese]
-
A.
dioceseType
chosen
Indicates the specific ecclesiastical category or kind of diocese that an entity belongs to.
-
B.
dioceseBishop
Indicates that a person serves as the bishop (ecclesiastical leader) of a specified diocese.
-
C.
administrativeDiocese
Indicates that one entity serves as the ecclesiastical administrative diocese responsible for the governance or oversight of another entity.
-
D.
dioceseGovernedEnd
Indicates the point in time or event at which a diocese ceases to be under the governance or authority of a particular governing entity.
-
E.
diocesanBishop
Indicates that one entity serves as the diocesan bishop—the chief ecclesiastical authority—responsible for the other entity (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_69e77e85254081908d79ee4e8715f283 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f7516d5b4081908588a6feb541f355 |
completed | May 3, 2026, 1:45 p.m. |
| PD | Predicate disambiguation | batch_69f74d40ebb081909daf60623e38f41d |
completed | May 3, 2026, 1:27 p.m. |
Created at: April 21, 2026, 11:06 p.m.