Triple

T2317731
Position Surface form Disambiguated ID Type / Status
Subject Northumberland E51104 entity
Predicate hasLargestTown P847 FINISHED
Object Ashington E256338 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: Ashington | Statement: [Northumberland, hasLargestTown, Ashington]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Ashington
Context triple: [Northumberland, hasLargestTown, Ashington]
  • A. Ashington chosen
    Ashington is a former coal-mining town in Northumberland, England, known for its industrial heritage and role in the region’s mining history.
  • B. Ashtead
    Ashtead is a large suburban village in Surrey, England, known for its residential character, local amenities, and proximity to the town of Leatherhead.
  • C. Apsley
    Apsley is a suburban village and residential area within the town of Hemel Hempstead in Hertfordshire, England, known for its canal-side setting and former paper mills.
  • D. Asthall
    Asthall is a small historic village in Oxfordshire, England, known for its Cotswold stone architecture and association with the Mitford family.
  • E. Highworth
    Highworth is a historic market town in Wiltshire, England, known for its elevated position and traditional architecture.
  • 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_69a88b074b908190ae983dbca7757d88 completed March 4, 2026, 7:41 p.m.
NER Named-entity recognition batch_69abc62fa60c8190b4859ce296ea4177 completed March 7, 2026, 6:31 a.m.
NED1 Entity disambiguation (via context triple) batch_69ae9610b420819095afb76347ddf9ee completed March 9, 2026, 9:42 a.m.
Created at: March 4, 2026, 7:49 p.m.