Triple

T33961778
Position Surface form Disambiguated ID Type / Status
Subject St Katharine Cree E870734 entity
Predicate governingDeanery P19542 FINISHED
Object City of London Deanery 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: City of London Deanery | Statement: [St Katharine Cree, governingDeanery, City of London Deanery]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: governingDeanery
Context triple: [St Katharine Cree, governingDeanery, City of London Deanery]
  • A. deanery chosen
    Indicates that one entity serves as the deanery (administrative office or jurisdiction of a dean) responsible for or associated with another entity.
  • B. 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.
  • C. archdeaconry
    Indicates that one entity holds the ecclesiastical office or jurisdiction of an archdeacon over another entity or area.
  • D. hasDeaneries
    Indicates that an institution or organization possesses one or more deaneries as part of its internal structure.
  • E. administrativeDiocese
    Indicates that one entity serves as the ecclesiastical administrative diocese responsible for the governance or oversight of another entity.
  • 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_6a00c8e617548190bba4cdfbb6f512e0 completed May 10, 2026, 6:05 p.m.
PD Predicate disambiguation batch_6a00c7e816b88190bd40f5ea2a768c8b completed May 10, 2026, 6:01 p.m.
Created at: May 1, 2026, 1:50 a.m.