Triple

T6479351
Position Surface form Disambiguated ID Type / Status
Subject River Lark E146148 entity
Predicate nearbySettlement P350 FINISHED
Object Icklingham E299768 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: Icklingham | Statement: [River Lark, nearbySettlement, Icklingham]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Icklingham
Context triple: [River Lark, nearbySettlement, Icklingham]
  • A. Icklingham chosen
    Icklingham is a small rural village in Suffolk, England, known for its historic churches and location within the Breckland landscape.
  • B. Aldwincle
    Aldwincle is a small village in Northamptonshire, England, best known as the birthplace of the poet and playwright John Dryden.
  • C. Etchingham
    Etchingham is a rural village and civil parish in East Sussex, England, known for its historic church and location in the Rother district.
  • D. Ickleford
    Ickleford is a small village and civil parish in North Hertfordshire, England, known for its rural character and historic parish church.
  • E. Flitcham
    Flitcham is a small rural village in Norfolk, England, known for its historic church and proximity to the royal Sandringham Estate.
  • 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_69c008fec7408190af7b146dc63d9750 completed March 22, 2026, 3:21 p.m.
NER Named-entity recognition batch_69c06a4e764c819086828bb841f588e0 completed March 22, 2026, 10:16 p.m.
NED1 Entity disambiguation (via context triple) batch_69c653aceb8c8190aff0abf15b049737 completed March 27, 2026, 9:53 a.m.
Created at: March 22, 2026, 4:51 p.m.