Triple

T14171926
Position Surface form Disambiguated ID Type / Status
Subject Tavistock Canal E351229 entity
Predicate servesCity P82 FINISHED
Object Tavistock E67261 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: Tavistock | Statement: [Tavistock Canal, servesCity, Tavistock]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Tavistock
Context triple: [Tavistock Canal, servesCity, Tavistock]
  • A. Tavistock chosen
    Tavistock is a historic market town in Devon, England, known for its medieval abbey remains and association with the Russell family, Dukes of Bedford.
  • B. Egremont
    Egremont is a district within the town of Wallasey on the Wirral Peninsula in Merseyside, England.
  • C. Egremont
    Egremont is a small rural town in southwestern Massachusetts known for its scenic Berkshire landscapes and historic New England character.
  • D. Shaftesbury
    Shaftesbury is a historic hilltop town in Dorset, England, known for its picturesque streets, including the famously steep, cobbled Gold Hill.
  • E. Portchester
    Portchester is a village in Hampshire, England, known for its historic Roman fort and as the birthplace of author Neil Gaiman.
  • 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_69d8278834a08190b0f1784e58d7b99c completed April 9, 2026, 10:26 p.m.
NER Named-entity recognition batch_69de61b5dcbc8190b0cfcce5e6c6d582 completed April 14, 2026, 3:48 p.m.
NED1 Entity disambiguation (via context triple) batch_69fd324772e4819092aef7826b39b144 completed May 8, 2026, 12:45 a.m.
Created at: April 10, 2026, 1:01 a.m.