Triple

T3507348
Position Surface form Disambiguated ID Type / Status
Subject Johann Daniel Salzmann E74106 entity
Predicate familyName P18 FINISHED
Object Salzmann E74106 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: Salzmann | Statement: [Johann Daniel Salzmann, familyName, Salzmann]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Salzmann
Context triple: [Johann Daniel Salzmann, familyName, Salzmann]
  • A. Salzmann chosen
    Salzmann is a German surname of likely occupational or locational origin, historically borne by various notable figures in fields such as education, theology, and the arts.
  • B. Salzman
    Salzman is the surname of Linda Salzman Sagan, an American artist and writer known for co-designing the Pioneer plaque sent into space.
  • C. Ussishkin
    Ussishkin is a Jewish family name most prominently associated with Zionist leader Menachem Ussishkin.
  • D. Zaslofsky
    Zaslofsky is a surname most notably associated with Max Zaslofsky, an early star guard in the National Basketball Association.
  • E. Hammann
    Hammann is a German-origin surname borne by various notable individuals in fields such as aviation, music, 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_69ad85ce7a9c81909ddc5cf0cb67a6e3 completed March 8, 2026, 2:21 p.m.
NER Named-entity recognition batch_69adbc0b635c81909bc95ba2562d8f94 completed March 8, 2026, 6:12 p.m.
NED1 Entity disambiguation (via context triple) batch_69b3bb7d6ab881909bf4c895646af259 completed March 13, 2026, 7:23 a.m.
Created at: March 8, 2026, 3:18 p.m.