Triple

T11490439
Position Surface form Disambiguated ID Type / Status
Subject Tenbury Wells E272393 entity
Predicate near P350 FINISHED
Object Ludlow E82172 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: Ludlow | Statement: [Tenbury Wells, near, Ludlow]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Ludlow
Context triple: [Tenbury Wells, near, Ludlow]
  • A. Ludlow chosen
    Ludlow is a historic market town in Shropshire, England, renowned for its well-preserved medieval architecture, Norman castle, and vibrant food culture.
  • B. Ludlow
    Ludlow is a small town in Windsor County, Vermont, best known as the home of the Okemo Mountain ski resort and a popular year-round outdoor recreation destination.
  • C. Ludlow
    Ludlow is an English-origin surname historically associated with various notable figures in politics, literature, and public life.
  • D. Ludlow
    Ludlow is a neighborhood in North Philadelphia, Pennsylvania, known for its residential character and proximity to major transit routes.
  • E. Castleton
    Castleton is a picturesque village in England’s Peak District, known for its surrounding hills, show caves, and historic Peveril Castle.
  • 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_69d6aae1b09881909ce2ded3fa0c14fa completed April 8, 2026, 7:22 p.m.
NER Named-entity recognition batch_69d85a20df608190992543b4d7006f8a completed April 10, 2026, 2:02 a.m.
NED1 Entity disambiguation (via context triple) batch_69e6046ec5108190a0294cc86e1b60cc completed April 20, 2026, 10:48 a.m.
Created at: April 8, 2026, 9:36 p.m.