Triple

T8584327
Position Surface form Disambiguated ID Type / Status
Subject St Mary the Virgin Church, Gamlingay E203264 entity
Predicate locatedIn P40 FINISHED
Object Gamlingay E203264 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: Gamlingay | Statement: [St Mary the Virgin Church, Gamlingay, locatedIn, Gamlingay]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Gamlingay
Context triple: [St Mary the Virgin Church, Gamlingay, locatedIn, Gamlingay]
  • A. Gamlingay chosen
    Gamlingay is a rural village and civil parish in Cambridgeshire, England, known for its historic architecture and surrounding countryside.
  • B. Hellingly
    Hellingly is a village and civil parish in East Sussex, England, known for its rural character and historic parish church.
  • C. Hawkenbury
    Hawkenbury is a residential suburb and community area of Royal Tunbridge Wells in Kent, England.
  • D. Hensingham
    Hensingham is a residential suburb of Whitehaven in Cumbria, England, known for its local community facilities and proximity to the town’s centre.
  • E. Ketteringham
    Ketteringham is a small village and civil parish in Norfolk, England, known for its rural character and historic parish church.
  • 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_69ca8329bb7c8190a63c643730839103 completed March 30, 2026, 2:05 p.m.
NER Named-entity recognition batch_69cbeb1ecc188190bbe2ab8d2423505b completed March 31, 2026, 3:41 p.m.
NED1 Entity disambiguation (via context triple) batch_69ce89bfb95c81909660460d5813fdaf completed April 2, 2026, 3:22 p.m.
Created at: March 30, 2026, 6:22 p.m.