Triple

T14367602
Position Surface form Disambiguated ID Type / Status
Subject Edward Hardwicke E356275 entity
Predicate familyName P18 FINISHED
Object Hardwicke E728279 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: Hardwicke | Statement: [Edward Hardwicke, familyName, Hardwicke]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Hardwicke
Context triple: [Edward Hardwicke, familyName, Hardwicke]
  • A. Hardwicke chosen
    Hardwicke is a given name most notably borne by Hardwicke Rawnsley, an English clergyman, conservationist, and co-founder of the National Trust.
  • B. Haverstock
    Haverstock is an electoral ward in the London Borough of Camden, England.
  • C. Egremont
    Egremont is a district within the town of Wallasey on the Wirral Peninsula in Merseyside, England.
  • D. Egremont
    Egremont is a small rural town in southwestern Massachusetts known for its scenic Berkshire landscapes and historic New England character.
  • E. Waddington
    Waddington is a village and civil parish in the North Kesteven district of Lincolnshire, England, known for its proximity to the city of Lincoln and RAF Waddington airbase.
  • 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_69d8279163a081908aec45c0e3f1e02f completed April 9, 2026, 10:26 p.m.
NER Named-entity recognition batch_69de8faf00e8819087d7100e9d8c1877 completed April 14, 2026, 7:04 p.m.
NED1 Entity disambiguation (via context triple) batch_69fd4c51bf888190b1776461884c4514 completed May 8, 2026, 2:37 a.m.
Created at: April 10, 2026, 1:15 a.m.