Triple

T16458386
Position Surface form Disambiguated ID Type / Status
Subject St Philip’s Church Litherland E399740 entity
Predicate region P40 FINISHED
Object Sefton E73864 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: Sefton | Statement: [St Philip’s Church Litherland, region, Sefton]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Sefton
Context triple: [St Philip’s Church Litherland, region, Sefton]
  • A. Sefton chosen
    Sefton is a metropolitan borough in North West England that includes coastal towns such as Southport and forms part of the Liverpool City Region.
  • B. Sefton
    Sefton is a small rural settlement in the Waimakariri District of Canterbury, New Zealand.
  • C. Wirral
    Wirral is a peninsula in North West England known for its mix of coastal towns, suburban areas, and countryside between the River Mersey and the River Dee.
  • D. Levenshulme
    Levenshulme is a residential suburb in south Manchester, England, known for its diverse community and vibrant local markets.
  • E. Ormskirk
    Ormskirk is a historic market town in West Lancashire, England, known for its traditional market, distinctive parish church, and proximity to both Liverpool and the surrounding countryside.
  • 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_69d87f2dac988190b74d6e185fa88ba4 completed April 10, 2026, 4:40 a.m.
NER Named-entity recognition batch_69e32d7ef5cc819084cfeb1a3e39d3cc completed April 18, 2026, 7:06 a.m.
NED1 Entity disambiguation (via context triple) batch_6a008a2363208190beb218e633d0627e completed May 10, 2026, 1:37 p.m.
Created at: April 10, 2026, 5:10 a.m.