Triple

T422938
Position Surface form Disambiguated ID Type / Status
Subject Thomas Putnam E8143 entity
Predicate familyName P18 FINISHED
Object Putnam E45179 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: Putnam | Statement: [Thomas Putnam, familyName, Putnam]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Putnam
Context triple: [Thomas Putnam, familyName, Putnam]
  • A. Putnam chosen
    Putnam is a prominent New England family name historically associated with several key figures in the Salem witch trials and early American colonial life.
  • B. Conant
    Conant is a surname most notably associated with James B. Conant, an influential American chemist, educator, and former president of Harvard University.
  • C. Belmont
    Belmont is a suburban town in Middlesex County, Massachusetts, known for its residential character and proximity to Boston.
  • D. Dartmouth
    Dartmouth was one of the merchant ships involved in the 1773 Boston Tea Party, a pivotal protest against British taxation in colonial America.
  • E. Hopkins
    Hopkins is a common English and Welsh surname borne by numerous notable figures across politics, the arts, and academia.
  • 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_69a2e7f1d1bc81909cf2dc9754a3c334 completed Feb. 28, 2026, 1:04 p.m.
NER Named-entity recognition batch_69a2eec200648190bcb9f1b98c8e9cdf completed Feb. 28, 2026, 1:33 p.m.
NED1 Entity disambiguation (via context triple) batch_69a42a15efe88190b1dc3337bd775723 completed March 1, 2026, 11:59 a.m.
Created at: Feb. 28, 2026, 1:11 p.m.