Triple

T8877554
Position Surface form Disambiguated ID Type / Status
Subject North Devon E211324 entity
Predicate containsSettlement P847 FINISHED
Object Lynton E435906 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: Lynton | Statement: [North Devon, containsSettlement, Lynton]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Lynton
Context triple: [North Devon, containsSettlement, Lynton]
  • A. Lynton chosen
    Lynton is a small coastal town in North Devon, England, known for its dramatic cliffside setting above Lynmouth and its Victorian-era cliff railway.
  • B. Leybourne
    Leybourne is a village and civil parish in Kent, England, known for its residential character and proximity to the town of West Malling.
  • C. Lansburgh
    Lansburgh is a surname most notably associated with G. Albert Lansburgh, an American architect known for his theater and commercial building designs in the early 20th century.
  • D. Queenborough
    Queenborough is a small historic port town in Kent, England, situated on the Isle of Sheppey and known for its maritime heritage and medieval origins.
  • E. Blyth
    Blyth is a coastal town and port in southeast Northumberland, England, known historically for coal mining and shipbuilding.
  • 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_69ca838e78748190934d82db3104f855 completed March 30, 2026, 2:07 p.m.
NER Named-entity recognition batch_69cc61496870819097c55c73aca62aac completed April 1, 2026, 12:05 a.m.
NED1 Entity disambiguation (via context triple) batch_69cfabaf57b88190a71d5303767ab517 completed April 3, 2026, 11:59 a.m.
Created at: March 30, 2026, 6:52 p.m.