Triple

T12537883
Position Surface form Disambiguated ID Type / Status
Subject Mutford E299747 entity
Predicate locatedNear P294 FINISHED
Object Barnby E299750 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: Barnby | Statement: [Mutford, locatedNear, Barnby]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Barnby
Context triple: [Mutford, locatedNear, Barnby]
  • A. Barnby chosen
    Barnby is a small rural village and civil parish located in the county of Suffolk in eastern England.
  • B. Barrowby
    Barrowby is a village in Lincolnshire, England, known for its rural character and proximity to the market town of Grantham.
  • C. Barnetby
    Barnetby is a village and railway junction in North Lincolnshire, England, known for its busy rail connections on routes across northern and eastern England.
  • D. Navenby
    Navenby is a historic village and civil parish in Lincolnshire, England, known for its traditional architecture and rural character.
  • E. Barmby on the Marsh
    Barmby on the Marsh is a small rural village and civil parish in the East Riding of Yorkshire, England, situated near the confluence of the River Derwent and the River Ouse.
  • 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_69d6ada707008190aaec1238117c9379 completed April 8, 2026, 7:33 p.m.
NER Named-entity recognition batch_69d9546ebf508190ae54857e4289c6e4 completed April 10, 2026, 7:50 p.m.
NED1 Entity disambiguation (via context triple) batch_69f6557a95d48190ac588807544f060f completed May 2, 2026, 7:50 p.m.
Created at: April 8, 2026, 9:57 p.m.