Triple

T13890191
Position Surface form Disambiguated ID Type / Status
Subject Burnham Thorpe E333949 entity
Predicate namedAfter P63 FINISHED
Object River Burn E286909 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: River Burn | Statement: [Burnham Thorpe, namedAfter, River Burn]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: River Burn
Context triple: [Burnham Thorpe, namedAfter, River Burn]
  • A. River Burn chosen
    River Burn is a small river in Norfolk, England, known for flowing through the village of Burnham Thorpe near the north Norfolk coast.
  • B. River Burn
    River Burn is a small river in North Yorkshire, England, known for flowing through Wensleydale before joining the River Ure.
  • C. River Rat
    The River Rat is a small river in Suffolk, England, that flows through villages such as Rattlesden before joining the River Gipping.
  • D. Đáy River
    Đáy River is a significant river in northern Vietnam that flows through several provinces and districts, serving as an important waterway and agricultural resource.
  • E. River Bogie
    River Bogie is a small river in Aberdeenshire, Scotland, known for flowing through the town of Huntly and contributing to the region’s rural landscape and local heritage.
  • 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_69de23a3a24881908d81d634622fbbcc completed April 14, 2026, 11:23 a.m.
NED1 Entity disambiguation (via context triple) batch_69f7ce71dcd481908f732542dfb1c3e3 completed May 3, 2026, 10:38 p.m.
Created at: April 9, 2026, 10:15 p.m.