Triple
T1280020
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Diocese of Worcester |
E27301
|
entity |
| Predicate | overseesChurches |
P12219
|
FINISHED |
| Object | Church of England churches in Worcestershire |
—
|
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: Church of England churches in Worcestershire | Statement: [Diocese of Worcester, overseesChurches, Church of England churches in Worcestershire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: overseesChurches Context triple: [Diocese of Worcester, overseesChurches, Church of England churches in Worcestershire]
-
A.
hasChurch
Indicates that a place or entity possesses, contains, or is associated with a church.
-
B.
hasNumberOfChurches
Indicates the relationship that specifies how many churches are associated with a given entity.
-
C.
religiousAdministration
chosen
Indicates that one entity holds authority or responsibility for managing, overseeing, or governing the religious affairs, practices, or institutions of another entity.
-
D.
associatedWithChurch
Indicates a relationship in which an entity has a connection, involvement, or affiliation with a church.
-
E.
viewOnChurch
Indicates that something has a view overlooking or directed toward a church.
- 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_69a496d3710c8190955dee8bc0dacb50 |
completed | March 1, 2026, 7:43 p.m. |
| NER | Named-entity recognition | batch_69a4c094eb4881909a33061339f91190 |
completed | March 1, 2026, 10:41 p.m. |
| PD | Predicate disambiguation | batch_69a4bee276d8819092f71c5a1140bb61 |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:50 p.m.