Triple

T5485015
Position Surface form Disambiguated ID Type / Status
Subject Godalming Parish Church of St Peter and St Paul E123557 entity
Predicate locatedIn P40 FINISHED
Object Godalming E24118 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: Godalming | Statement: [Godalming Parish Church of St Peter and St Paul, locatedIn, Godalming]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Godalming
Context triple: [Godalming Parish Church of St Peter and St Paul, locatedIn, Godalming]
  • A. Godalming chosen
    Godalming is a historic market town in southeast England known for its picturesque streets, riverside setting, and role as a commuter hub for London.
  • B. Oakengates
    Oakengates is a small town in Shropshire, England, now effectively part of the Telford urban area.
  • C. Gamesley
    Gamesley is a residential area and former council estate on the outskirts of Glossop in Derbyshire, England.
  • D. Ingatestone
    Ingatestone is a historic village and civil parish in southeast England known for its traditional architecture and commuter links to London.
  • E. Kilndown
    Kilndown is a small rural village in Kent, England, known for its historic church and woodland surroundings.
  • 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_69bd4648883481909e9775d43300c5fa completed March 20, 2026, 1:06 p.m.
NER Named-entity recognition batch_69bd9260d90c819087f34ab24662575d completed March 20, 2026, 6:30 p.m.
NED1 Entity disambiguation (via context triple) batch_69bf6c812d4c8190a22f76b787ab0f10 completed March 22, 2026, 4:13 a.m.
Created at: March 20, 2026, 2:10 p.m.