Triple

T13884750
Position Surface form Disambiguated ID Type / Status
Subject Rushden E333811 entity
Predicate hasPostTown P2711 FINISHED
Object RUSHDEN E333811 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: RUSHDEN | Statement: [Rushden, hasPostTown, RUSHDEN]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: RUSHDEN
Context triple: [Rushden, hasPostTown, RUSHDEN]
  • A. Rushden
    Rushden is a small rural village in the North Hertfordshire district of Hertfordshire, England.
  • B. Rushden chosen
    Rushden is a market town in the East Midlands of England known for its historical shoe and boot manufacturing industry and later retail and leisure developments.
  • C. Ruddington
    Ruddington is a large village in Nottinghamshire, England, known for its historic framework knitting industry and the Great Central Railway heritage centre.
  • D. Rattlesden
    Rattlesden is a small rural village and civil parish in the county of Suffolk in eastern England.
  • E. Rusthall
    Rusthall is a village and civil parish in Kent, England, known for its sandstone rock formations and proximity to the spa town of Royal Tunbridge Wells.
  • 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_69d81c5dd2d48190b7a5fc1e009de936 completed April 9, 2026, 9:38 p.m.
NER Named-entity recognition batch_69de0bea4d248190bcbcea9ea875c5f9 completed April 14, 2026, 9:42 a.m.
NED1 Entity disambiguation (via context triple) batch_69f7c716166c8190a6323f8c01de06a5 completed May 3, 2026, 10:07 p.m.
Created at: April 9, 2026, 10:15 p.m.