Triple

T17576988
Position Surface form Disambiguated ID Type / Status
Subject Barnetby E428094 entity
Predicate near P350 FINISHED
Object Brigg NE NERFINISHED

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: Brigg | Statement: [Barnetby, near, Brigg]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Brigg
Context triple: [Barnetby, near, Brigg]
  • A. Brigg chosen
    Brigg is a small historic market town in North Lincolnshire, England, known for its traditional markets and rural character.
  • B. Richborough
    Richborough is a historic site in Kent, England, known for its significant Roman remains and its role as a key gateway to Roman Britain.
  • C. Aberporth
    Aberporth is a coastal village in Ceredigion, Wales, known for its sandy beaches, seaside tourism, and scenic views over Cardigan Bay.
  • D. Hildenborough
    Hildenborough is a village in Kent, England, situated near Tonbridge and known for its commuter links to London and surrounding towns.
  • E. King's Lynn
    King's Lynn is a historic market and port town in Norfolk, England, known for its medieval architecture and long-standing role as a regional commercial center.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69d889e0385081908a04b66f4dd4bd0d completed April 10, 2026, 5:25 a.m.
NER Named-entity recognition batch_69e463ca76848190a7beb6deb4b0f1a4 completed April 19, 2026, 5:10 a.m.
Created at: April 10, 2026, 5:50 a.m.