Triple

T13954629
Position Surface form Disambiguated ID Type / Status
Subject Littondale E335622 entity
Predicate hasRoadAccessFrom P22549 FINISHED
Object Arncliffe E1071311 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: Arncliffe | Statement: [Littondale, hasRoadAccessFrom, Arncliffe]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Arncliffe
Context triple: [Littondale, hasRoadAccessFrom, Arncliffe]
  • A. Arncliffe chosen
    Arncliffe is a small, picturesque village in Littondale in the Yorkshire Dales, known for its traditional stone buildings and scenic rural setting.
  • B. Briercliffe
    Briercliffe is a civil parish and rural village area in Lancashire, England, situated within the Borough of Burnley.
  • C. Henfield
    Henfield is a large historic village and civil parish in the Horsham District of West Sussex, England, known for its rural character and community amenities.
  • D. Staincliffe
    Staincliffe is a residential suburb within the town of Batley in West Yorkshire, England.
  • E. Langcliffe
    Langcliffe is a small village in North Yorkshire, England, situated in the scenic Yorkshire Dales near the market town of Settle.
  • 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_69d81c6081b88190b53e317c3370c8fe completed April 9, 2026, 9:38 p.m.
NER Named-entity recognition batch_69de2e78a4a481908e438745631a43c0 completed April 14, 2026, 12:09 p.m.
NED1 Entity disambiguation (via context triple) batch_69fbac8c06ec8190a6dfceab55da5b30 completed May 6, 2026, 9:03 p.m.
Created at: April 9, 2026, 10:17 p.m.