Triple
T33961777
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | St Katharine Cree |
E870734
|
entity |
| Predicate | governingArchdeaconry |
P44486
|
FINISHED |
| Object | Archdeaconry of London |
—
|
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: Archdeaconry of London | Statement: [St Katharine Cree, governingArchdeaconry, Archdeaconry of London]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: governingArchdeaconry Context triple: [St Katharine Cree, governingArchdeaconry, Archdeaconry of London]
-
A.
archdeaconry
Indicates that one entity holds the ecclesiastical office or jurisdiction of an archdeacon over another entity or area.
-
B.
belongsToArchdeaconry
chosen
Indicates that one ecclesiastical unit or entity is administratively part of, or under the jurisdiction of, a specific archdeaconry.
-
C.
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.
-
D.
governingDioceseHistorical
Indicates that one diocese historically exercised governing authority or jurisdiction over another ecclesiastical entity.
-
E.
overseesParish
Indicates that one entity has administrative or supervisory responsibility over a parish.
- 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_69f3499ce8e88190b66e1d49ad8c7037 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a00c59b03dc8190870f0dd24603a1ef |
completed | May 10, 2026, 5:51 p.m. |
| PD | Predicate disambiguation | batch_6a00c5178bc88190b2a0e03f38314035 |
completed | May 10, 2026, 5:49 p.m. |
Created at: May 1, 2026, 1:50 a.m.