Triple

T6490504
Position Surface form Disambiguated ID Type / Status
Subject Godalming E148022 entity
Predicate hasNeighbour P5707 FINISHED
Object Farncombe E123558 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: Farncombe | Statement: [Godalming, hasNeighbour, Farncombe]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Farncombe
Context triple: [Godalming, hasNeighbour, Farncombe]
  • A. Farncombe chosen
    Farncombe is a village in Surrey, England, situated just north of the town of Godalming.
  • B. Seacombe
    Seacombe is a small coastal bay and cove on the Jurassic Coast in Dorset, England, known for its rugged cliffs and scenic walking paths.
  • C. Seacombe
    Seacombe is a riverside district and ferry terminal on the Wirral Peninsula in England, serving as a key Mersey crossing point to Liverpool.
  • D. Farnworth
    Farnworth is a town in Greater Manchester, England, historically part of Lancashire and now largely residential with local industry and transport links to nearby urban centers.
  • E. Cambourne
    Cambourne is a modern, rapidly growing new town in Cambridgeshire, England, developed in the late 20th century and known for its planned residential communities and local amenities.
  • 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_69c009088f3081909cd467b05919de30 completed March 22, 2026, 3:21 p.m.
NER Named-entity recognition batch_69c06a9a8d8481908d88e5c9f0c773f7 completed March 22, 2026, 10:18 p.m.
NED1 Entity disambiguation (via context triple) batch_69c653bcb63081908be29abd0084d266 completed March 27, 2026, 9:54 a.m.
Created at: March 22, 2026, 4:53 p.m.