Triple

T21014450
Position Surface form Disambiguated ID Type / Status
Subject Kingsdale E517635 entity
Predicate hasAccessRoadFrom P22549 FINISHED
Object Ingleton 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: Ingleton | Statement: [Kingsdale, hasAccessRoadFrom, Ingleton]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Ingleton
Context triple: [Kingsdale, hasAccessRoadFrom, Ingleton]
  • A. Ingleton chosen
    Ingleton is a civil parish and village in North Yorkshire, England, known for its scenic limestone landscapes, waterfalls, and proximity to the Yorkshire Dales.
  • B. Mirfield
    Mirfield is a small town in West Yorkshire, England, known for its position on major rail routes and its historic textile industry.
  • C. Austwick
    Austwick is a small village and civil parish in North Yorkshire, England, situated within the scenic Yorkshire Dales.
  • D. Haltwhistle
    Haltwhistle is a small town in Northumberland, England, known as a gateway to Hadrian’s Wall and the surrounding Tyne Valley countryside.
  • E. Heighington
    Heighington is a village in Lincolnshire, England, known for its historic character and proximity to the city of Lincoln.
  • 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_69e0b50262b081909bc488937145eb73 completed April 16, 2026, 10:08 a.m.
NER Named-entity recognition batch_69e6fc5764188190829de6f5abd6e00f completed April 21, 2026, 4:25 a.m.
Created at: April 16, 2026, 1:54 p.m.