Triple

T15428252
Position Surface form Disambiguated ID Type / Status
Subject Sir Ernest Debenham E369568 entity
Predicate familyName P18 FINISHED
Object Debenham E299719 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: Debenham | Statement: [Sir Ernest Debenham, familyName, Debenham]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Debenham
Context triple: [Sir Ernest Debenham, familyName, Debenham]
  • A. Debenham chosen
    Debenham is a historic village and civil parish in the Mid Suffolk district of Suffolk, England, known for its traditional architecture and rural character.
  • B. Rendham
    Rendham is a small rural village and civil parish located in the county of Suffolk in eastern England.
  • C. Hellesdon
    Hellesdon is a suburban village and civil parish on the outskirts of Norwich in Norfolk, England, known for its residential character and local amenities.
  • D. Downham
    Downham is a residential district in southeast London known for its interwar housing estates and suburban character within the London Borough of Lewisham.
  • E. Downham
    Downham is a picturesque rural village in Lancashire, England, known for its unspoiled traditional character and scenic setting near Pendle Hill.
  • 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_69d85a1849f48190bf898068b2806fae completed April 10, 2026, 2:02 a.m.
NER Named-entity recognition batch_69e03ec31f4881908b26ff7c381d7bc9 completed April 16, 2026, 1:43 a.m.
NED1 Entity disambiguation (via context triple) batch_69ff1a8099448190be71f7b649c7e545 completed May 9, 2026, 11:29 a.m.
Created at: April 10, 2026, 3:20 a.m.