Triple

T17137112
Position Surface form Disambiguated ID Type / Status
Subject Daylesford E415866 entity
Predicate hasChurch P15000 FINISHED
Object Church of St Peter E851454 NE 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 St Peter | Statement: [Daylesford, hasChurch, Church of St Peter]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: Church of St Peter
Context triple: [Daylesford, hasChurch, Church of St Peter]
  • A. Church of St Peter chosen
    The Church of St Peter is a historic Anglican parish church serving the village of Daylesford in Gloucestershire, England.
  • B. Church of St Peter
    The Church of St Peter is a historic parish church serving the village of Wenhaston in Suffolk, England.
  • C. Church of St Peter
    The Church of St Peter is a historic Christian parish church serving the village of Cornwell in England.
  • D. Church of St Peter
    The Church of St Peter in Antakya is an ancient cave church considered one of the earliest Christian worship sites and traditionally associated with the Apostle Peter.
  • E. Church of St Peter
    The Church of St Peter is a historic parish church serving the village community of Coton in Cambridgeshire, England.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69d886d15af4819092f92f8a129763e6 completed April 10, 2026, 5:12 a.m.
NER Named-entity recognition batch_69e3f2d0628081908e0160290041fe89 completed April 18, 2026, 9:08 p.m.
NED1 Entity disambiguation (via context triple) batch_6a014152da008190bbbff4147cfd8c5b completed May 11, 2026, 2:39 a.m.
Created at: April 10, 2026, 5:36 a.m.