Triple

T20029587
Position Surface form Disambiguated ID Type / Status
Subject Joffe E495084 entity
Predicate hasVariant P455 FINISHED
Object Yoffe 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: Yoffe | Statement: [Joffe, hasVariant, Yoffe]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Yoffe
Context triple: [Joffe, hasVariant, Yoffe]
  • A. Joffe chosen
    Joffe is a surname most notably associated with Adolf Joffe, a prominent early 20th-century Russian revolutionary and diplomat.
  • B. Yaffe
    Yaffe is a surname of Jewish origin borne by various individuals, including those in public, academic, and cultural fields.
  • C. Savyon
    Savyon is an affluent residential town in central Israel known for its spacious villas, high standard of living, and proximity to Tel Aviv.
  • D. Pfefferberg
    Pfefferberg is a surname most notably associated with Poldek Pfefferberg, a Holocaust survivor who played a key role in bringing Oskar Schindler’s story to public attention.
  • E. Yehudi
    Yehudi is a masculine given name most famously associated with the renowned violinist Yehudi Menuhin.
  • 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_69da626bfd288190aa5d65098b6433ae completed April 11, 2026, 3:02 p.m.
NER Named-entity recognition batch_69e662908df081909a6c8ccf0dd90fff completed April 20, 2026, 5:29 p.m.
Created at: April 11, 2026, 3:36 p.m.