Triple

T14277371
Position Surface form Disambiguated ID Type / Status
Subject Lyme Regis E353948 entity
Predicate near P350 FINISHED
Object Axminster E573293 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: Axminster | Statement: [Lyme Regis, near, Axminster]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Axminster
Context triple: [Lyme Regis, near, Axminster]
  • A. Axminster chosen
    Axminster is a historic market town in East Devon, England, best known for its traditional carpet industry and picturesque rural surroundings.
  • B. Warminster
    Warminster is a suburban township in Bucks County, Pennsylvania, known for its residential communities, local commerce, and small general-aviation airport.
  • C. Warminster
    Warminster is a market town in Wiltshire, England, known for its historic architecture, surrounding countryside, and role as a local transport and service hub.
  • D. Corringham
    Corringham is a small town and civil parish in the unitary authority of Thurrock in Essex, England, with historic roots and a largely residential character.
  • E. Maxton
    Maxton is the given first name of English actor and musician Max Beesley.
  • 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_69d8278d25148190abf1a8c8f5f533ad completed April 9, 2026, 10:26 p.m.
NER Named-entity recognition batch_69de6583f0ec81909ebfc7a2c6351ff8 completed April 14, 2026, 4:04 p.m.
NED1 Entity disambiguation (via context triple) batch_69fd326f62b4819084b1e984678991ae completed May 8, 2026, 12:46 a.m.
Created at: April 10, 2026, 1:10 a.m.