Triple

T8730255
Position Surface form Disambiguated ID Type / Status
Subject South Anston E207236 entity
Predicate adjacentTo P224 FINISHED
Object North Anston E206818 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: North Anston | Statement: [South Anston, adjacentTo, North Anston]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: North Anston
Context triple: [South Anston, adjacentTo, North Anston]
  • A. North Anston chosen
    North Anston is a village in South Yorkshire, England, historically notable for its limestone quarries and rural character.
  • B. South Anston
    South Anston is a village in South Yorkshire, England, historically notable for its limestone quarries that supplied stone for major 19th-century construction projects.
  • C. Anderston
    Anderston is a district in Glasgow, Scotland, known for its central location near the River Clyde and mix of residential, commercial, and transport links.
  • D. Baillieston
    Baillieston is a residential suburb in the east end of Glasgow, Scotland, situated near major transport routes including the M73 motorway.
  • E. Bearsden
    Bearsden is an affluent suburban town in East Dunbartonshire, Scotland, known for its residential character and proximity to Glasgow.
  • 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_69ca8358e4008190898471a59b96c301 completed March 30, 2026, 2:06 p.m.
NER Named-entity recognition batch_69cc5d26d280819085e15d4917c2b9a5 completed March 31, 2026, 11:47 p.m.
NED1 Entity disambiguation (via context triple) batch_69cf88dc7ba88190865957c8d344fa00 completed April 3, 2026, 9:31 a.m.
Created at: March 30, 2026, 6:37 p.m.