Triple

T2420913
Position Surface form Disambiguated ID Type / Status
Subject Rudolf Einstein E53414 entity
Predicate relative P37 FINISHED
Object Hermann Einstein E96524 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: Hermann Einstein | Statement: [Rudolf Einstein, relative, Hermann Einstein]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Hermann Einstein
Context triple: [Rudolf Einstein, relative, Hermann Einstein]
  • A. Hermann Einstein chosen
    Hermann Einstein was a German engineer and businessman best known as the father of physicist Albert Einstein.
  • B. Hans Albert Einstein
    Hans Albert Einstein was a Swiss-American engineer and educator known for his contributions to hydraulic engineering and as the second son of physicist Albert Einstein.
  • C. Eduard Einstein
    Eduard Einstein was the younger son of physicist Albert Einstein, known for his early promise in psychiatry and his later struggles with severe mental illness.
  • D. Bernhard Caesar Einstein
    Bernhard Caesar Einstein was a Swiss-American engineer and the only grandchild of Albert Einstein to become a physicist.
  • E. Rudolf Einstein
    Rudolf Einstein was the father of Elsa Einstein, who was both the second wife and cousin of physicist Albert Einstein.
  • 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_69ab495c44d48190b7235b23719bc3f6 completed March 6, 2026, 9:38 p.m.
NER Named-entity recognition batch_69abc96f97e08190978b2d873ab88859 completed March 7, 2026, 6:45 a.m.
NED1 Entity disambiguation (via context triple) batch_69af5cd2e9808190aa124c6051d1fc98 completed March 9, 2026, 11:50 p.m.
Created at: March 6, 2026, 9:42 p.m.