Triple

T6626376
Position Surface form Disambiguated ID Type / Status
Subject St Paul’s Church, Addlestone E149813 entity
Predicate hasParish P35 FINISHED
Object Addlestone parish E28020 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: Addlestone parish | Statement: [St Paul’s Church, Addlestone, hasParish, Addlestone parish]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Addlestone parish
Context triple: [St Paul’s Church, Addlestone, hasParish, Addlestone parish]
  • A. Addlestone chosen
    Addlestone is a suburban town in southeast England known for its residential character and proximity to London.
  • B. Aylestone
    Aylestone is a suburban area of Leicester, England, known for its historic village core and riverside setting along the River Soar.
  • C. Binsted parish
    Binsted parish is a rural civil and ecclesiastical parish in West Sussex, England, centered on the historic Holy Cross Church and its surrounding village community.
  • D. Hoddlesden
    Hoddlesden is a small village in Lancashire, England, situated in a rural valley setting and historically associated with textile manufacturing.
  • E. Ashingdon
    Ashingdon is a village and civil parish in Essex, England, known for its historic church and connections to the Battle of Assandun in 1016.
  • 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_69c687ee50048190aa151765bef16193 completed March 27, 2026, 1:36 p.m.
NER Named-entity recognition batch_69c6afa0feb0819099629c0fba590a05 completed March 27, 2026, 4:26 p.m.
NED1 Entity disambiguation (via context triple) batch_69c6e44d356c8190ad4f2a617c3de4af completed March 27, 2026, 8:10 p.m.
Created at: March 27, 2026, 1:58 p.m.