Triple

T8712745
Position Surface form Disambiguated ID Type / Status
Subject Anston E206816 entity
Predicate hasPart P35 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: [Anston, hasPart, North Anston]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: North Anston
Context triple: [Anston, hasPart, 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_69ca83572d4881909bef3be2b578d539 completed March 30, 2026, 2:06 p.m.
NER Named-entity recognition batch_69cc5c32aebc8190ba19299ce9a18efd completed March 31, 2026, 11:43 p.m.
NED1 Entity disambiguation (via context triple) batch_69cf28cd239c81909d1feb98b652eb26 completed April 3, 2026, 2:41 a.m.
Created at: March 30, 2026, 6:35 p.m.