Triple

T22019027
Position Surface form Disambiguated ID Type / Status
Subject Nachman E543788 entity
Predicate hasVariant P455 FINISHED
Object Nachum
Nachum is a Hebrew given name, often considered a variant of Nachman, traditionally borne by Jewish men and associated with biblical and rabbinic figures.
E543788 NE FINISHED

How this triple was built (4 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: Nachum | Statement: [Nachman, hasVariant, Nachum]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Nachum
Context triple: [Nachman, hasVariant, Nachum]
  • A. Shmuel
    Shmuel is the Hebrew form of the biblical name Samuel, commonly used in Jewish religious and cultural contexts.
  • B. Nachman
    Nachman is a masculine given name of Hebrew origin, traditionally used in Jewish communities.
  • C. Menachem
    Menachem is a Hebrew given name commonly associated with Jewish men, notably borne by figures such as Israeli Prime Minister Menachem Begin.
  • D. Shlomo
    Shlomo is the Hebrew name for King Solomon, the biblical monarch renowned for his wisdom, wealth, and the construction of the First Temple in Jerusalem.
  • E. Chaim
    Chaim is a given name notably borne by Chaim Weizmann, the first President of the State of Israel and a prominent Zionist leader and chemist.
  • F. None of above. chosen
  • G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Nachum
Triple: [Nachman, hasVariant, Nachum]
Generated description
Nachum is a Hebrew given name, often considered a variant of Nachman, traditionally borne by Jewish men and associated with biblical and rabbinic figures.
NED2 Entity disambiguation (via description) gpt-5-mini-2025-08-07
Target entity: Nachum
Target entity description: Nachum is a Hebrew given name, often considered a variant of Nachman, traditionally borne by Jewish men and associated with biblical and rabbinic figures.
  • A. Shmuel
    Shmuel is the Hebrew form of the biblical name Samuel, commonly used in Jewish religious and cultural contexts.
  • B. Nachman chosen
    Nachman is a masculine given name of Hebrew origin, traditionally used in Jewish communities.
  • C. Menachem
    Menachem is a Hebrew given name commonly associated with Jewish men, notably borne by figures such as Israeli Prime Minister Menachem Begin.
  • D. Shlomo
    Shlomo is the Hebrew name for King Solomon, the biblical monarch renowned for his wisdom, wealth, and the construction of the First Temple in Jerusalem.
  • E. Chaim
    Chaim is a given name notably borne by Chaim Weizmann, the first President of the State of Israel and a prominent Zionist leader and chemist.
  • F. None of above.

Provenance (5 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_69e11e2e8ea4819084210fe06d3a1b8d completed April 16, 2026, 5:36 p.m.
NER Named-entity recognition batch_69f127c5929881908458d07bd33c5edd completed April 28, 2026, 9:33 p.m.
NED1 Entity disambiguation (via context triple) batch_6a0a7b63c3748190b6b9110929db9449 completed May 18, 2026, 2:37 a.m.
NEDg Description generation batch_6a0a7c55ca248190b99a81970626b1f0 completed May 18, 2026, 2:41 a.m.
NED2 Entity disambiguation (via description) batch_6a0a7d1995408190a7b41daba0fd241e completed May 18, 2026, 2:44 a.m.
Created at: April 16, 2026, 8:23 p.m.