Triple

T21251446
Position Surface form Disambiguated ID Type / Status
Subject David Puttnam E523753 entity
Predicate familyName P18 FINISHED
Object Puttnam 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: Puttnam | Statement: [David Puttnam, familyName, Puttnam]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Puttnam
Context triple: [David Puttnam, familyName, Puttnam]
  • A. Puttnam chosen
    Puttnam is a surname most notably associated with British film producer and politician David Puttnam.
  • B. Rennahan
    Rennahan is a surname most notably associated with Ray Rennahan, an American cinematographer known for his pioneering work with Technicolor.
  • C. Tilghman
    Tilghman is a masculine given name of English origin that has been borne by various notable American figures, including politicians and military officers.
  • D. Tilghman
    Tilghman is a surname most notably associated with Shirley M. Tilghman, a prominent molecular biologist and former president of Princeton University.
  • E. Tolan
    Tolan is a surname most notably associated with American television producer, writer, and director Peter Tolan.
  • 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_69e0b5146c108190adc9adb73e90abff completed April 16, 2026, 10:08 a.m.
NER Named-entity recognition batch_69e7359e90d881909b3153f1e7213c5c completed April 21, 2026, 8:30 a.m.
Created at: April 16, 2026, 3:57 p.m.