Triple

T20587005
Position Surface form Disambiguated ID Type / Status
Subject Bruce Reitherman E505813 entity
Predicate familyName P18 FINISHED
Object Reitherman 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: Reitherman | Statement: [Bruce Reitherman, familyName, Reitherman]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Reitherman
Context triple: [Bruce Reitherman, familyName, Reitherman]
  • A. Reitherman chosen
    Reitherman is the surname of Wolfgang Reitherman, a prominent Disney animator and director known for his work on many classic animated films.
  • B. Erdman
    Erdman is a masculine given name most notably borne by Disney story artist and screenwriter Erdman Penner.
  • C. Furthman
    Furthman is a surname most notably associated with American screenwriter Jules Furthman, known for his work on classic Hollywood films.
  • D. Yetman
    Yetman is a small rural town in northern New South Wales, Australia, known for its agricultural surroundings and location near the Macintyre River.
  • E. Kraushaar
    Kraushaar is a surname most notably associated with Raoul Kraushaar, an American film and television composer active in the mid-20th century.
  • 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_69e0b4b9669c8190b8e81fc72817d42c completed April 16, 2026, 10:06 a.m.
NER Named-entity recognition batch_69e6a977fb18819085fee5cf5d45c1b0 completed April 20, 2026, 10:32 p.m.
Created at: April 16, 2026, 11:40 a.m.