Triple

T8712849
Position Surface form Disambiguated ID Type / Status
Subject North Anston E206818 entity
Predicate hasNearbyAttraction P2064 FINISHED
Object Anston Brook E753785 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: Anston Brook | Statement: [North Anston, hasNearbyAttraction, Anston Brook]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Anston Brook
Context triple: [North Anston, hasNearbyAttraction, Anston Brook]
  • A. Anston Brook chosen
    Anston Brook is a small watercourse in South Yorkshire, England, that flows through the village of Anston and its surrounding countryside.
  • B. Cornbrook
    Cornbrook is a major Metrolink tram interchange area in Manchester, England, providing key connections between multiple tram lines.
  • C. Asthall
    Asthall is a small historic village in Oxfordshire, England, known for its Cotswold stone architecture and association with the Mitford family.
  • D. Edstaston
    Edstaston is a small rural parish and village in Shropshire, England, known for its historic church and agricultural surroundings.
  • E. Atherstone‑on‑Stour
    Atherstone‑on‑Stour is a small village in Warwickshire, England, situated in a rural setting near the River Mease.
  • 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_69cf42998df88190a6eba28c2efb2030 completed April 3, 2026, 4:31 a.m.
Created at: March 30, 2026, 6:35 p.m.