Triple

T13565121
Position Surface form Disambiguated ID Type / Status
Subject Brigg E324013 entity
Predicate nearTo P350 FINISHED
Object Scunthorpe E190757 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: Scunthorpe | Statement: [Brigg, nearTo, Scunthorpe]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Scunthorpe
Context triple: [Brigg, nearTo, Scunthorpe]
  • A. Scunthorpe chosen
    Scunthorpe is an industrial town in North Lincolnshire, England, historically known for its steel production.
  • B. Yorkton
    Yorkton is a small city in southeastern Saskatchewan, Canada, known as a regional hub for agriculture and services.
  • C. Doncaster
    Doncaster is a large town and metropolitan borough in South Yorkshire, England, known historically for its railway heritage, horse racing, and role as a regional commercial center.
  • D. Corby
    Corby is a town in Northamptonshire, England, known for its steel industry heritage and significant Scottish community.
  • E. Todmorden
    Todmorden is a market town in West Yorkshire, England, known for its industrial heritage, surrounding Pennine countryside, and community-led urban agriculture initiatives.
  • 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_69d8076830b48190910a902bae5888e2 completed April 9, 2026, 8:09 p.m.
NER Named-entity recognition batch_69dbb00cecd48190a9a2caff3d424817 completed April 12, 2026, 2:45 p.m.
NED1 Entity disambiguation (via context triple) batch_69f75daf1bfc8190bf22eb9ef242f54f completed May 3, 2026, 2:37 p.m.
Created at: April 9, 2026, 9:47 p.m.