Triple

T5598113
Position Surface form Disambiguated ID Type / Status
Subject Waverley E147046 entity
Predicate hasTown P847 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: [Waverley, hasTown, Godalming]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Godalming
Context triple: [Waverley, hasTown, 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. Mortmain
    Mortmain is a minor philosophical and religious figure in Herman Melville’s epic poem "Clarel," embodying skeptical and intellectual perspectives within the work’s spiritual debates.
  • C. Oakengates
    Oakengates is a small town in Shropshire, England, now effectively part of the Telford urban area.
  • D. Gamesley
    Gamesley is a residential area and former council estate on the outskirts of Glossop in Derbyshire, England.
  • E. Ingatestone
    Ingatestone is a historic village and civil parish in southeast England known for its traditional architecture and commuter links to London.
  • 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_69c009043d648190a7af89698ccf1e3e completed March 22, 2026, 3:21 p.m.
NER Named-entity recognition batch_69c020d82870819087f9591b5a1021ce completed March 22, 2026, 5:03 p.m.
NED1 Entity disambiguation (via context triple) batch_69c05a045c4881909a3e48a242db5d22 completed March 22, 2026, 9:07 p.m.
Created at: March 22, 2026, 3:38 p.m.