Triple

T16276385
Position Surface form Disambiguated ID Type / Status
Subject All Saints Church, Edmonton E395138 entity
Predicate hasName P744 FINISHED
Object All Saints Church unclear NED1 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: All Saints Church | Statement: [All Saints Church, Edmonton, hasName, All Saints Church]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: All Saints Church
Context triple: [All Saints Church, Edmonton, hasName, All Saints Church]
  • A. All Saints Church
    All Saints Church is a historic Orthodox church located within the Kyiv Pechersk Lavra monastic complex in Kyiv, Ukraine.
  • B. All Saints Church
    All Saints Church is a historic Christian church located in the city of Nizhyn, Ukraine.
  • C. All Saints Church
    All Saints Church is a historic Christian church and notable architectural landmark located in the Czech town of Litoměřice.
  • D. All Saints Church
    All Saints Church is a Christian place of worship serving the community of Hale Barns in Greater Manchester, England.
  • E. All Saints Church
    All Saints Church is a historic Anglican parish church serving the village community of Shouldham in Norfolk, England.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide. chosen

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_69d87f221d8081909b0b2063e7528ba2 completed April 10, 2026, 4:40 a.m.
NER Named-entity recognition batch_69e2460ea5a4819099f779288a754c8d completed April 17, 2026, 2:39 p.m.
NED1 Entity disambiguation (via context triple) batch_6a001f90d4088190915d701978f018a5 completed May 10, 2026, 6:02 a.m.
Created at: April 10, 2026, 5:05 a.m.