Triple

T21128129
Position Surface form Disambiguated ID Type / Status
Subject Wedmore E520611 entity
Predicate locatedNear P294 FINISHED
Object Axbridge NE NERFINISHED

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: Axbridge | Statement: [Wedmore, locatedNear, Axbridge]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Axbridge
Context triple: [Wedmore, locatedNear, Axbridge]
  • A. Axbridge chosen
    Axbridge is a small historic town in Somerset, England, known for its medieval square and proximity to the Mendip Hills.
  • B. Heybridge
    Heybridge is a small coastal locality in Tasmania, Australia, situated near the city of Burnie.
  • C. Heybridge
    Heybridge is a village and civil parish in the Maldon district of Essex, England, known for its proximity to the River Blackwater and its mix of residential and light industrial areas.
  • D. Greenbridge
    Greenbridge is a residential and commercial area forming part of the wider Stratton St Margaret district near Swindon in Wiltshire, England.
  • E. Horsebridge
    Horsebridge is a historic bridge spanning the River Tamar on the border between Devon and Cornwall in southwest England.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69e0b50a623881909c0bbaf4f2c055e7 completed April 16, 2026, 10:08 a.m.
NER Named-entity recognition batch_69e7223a7a588190a01a66921b79b98b completed April 21, 2026, 7:07 a.m.
Created at: April 16, 2026, 2:56 p.m.