Triple

T18623879
Position Surface form Disambiguated ID Type / Status
Subject William Haseldine Pepys E455226 entity
Predicate hasFamilyName P18 FINISHED
Object Pepys 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: Pepys | Statement: [William Haseldine Pepys, hasFamilyName, Pepys]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Pepys
Context triple: [William Haseldine Pepys, hasFamilyName, Pepys]
  • A. Pepys chosen
    Pepys is a notable English surname most famously associated with Samuel Pepys, the 17th-century diarist and naval administrator.
  • B. Talbot Pepys
    Talbot Pepys was a 17th-century English lawyer and politician, best known as a member of the prominent Pepys family that included the diarist Samuel Pepys.
  • C. Samuel Pepys
    Samuel Pepys was a 17th-century English naval administrator and diarist whose detailed journals provide a vivid firsthand account of Restoration-era London.
  • D. John Pepys
    John Pepys was a member of the Pepys family in 17th-century England, known primarily as a relative of the famed diarist and naval administrator Samuel Pepys.
  • E. William Haseldine Pepys
    William Haseldine Pepys was an English lawyer and diarist of the late 18th and early 19th centuries, known for his detailed journals and connections within London’s intellectual and social circles.
  • 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_69d8d38cc7948190a55ea64e5638994e completed April 10, 2026, 10:40 a.m.
NER Named-entity recognition batch_69e54f02dc248190a82341eeb2473593 completed April 19, 2026, 9:54 p.m.
Created at: April 10, 2026, 11:46 a.m.