Triple

T645831
Position Surface form Disambiguated ID Type / Status
Subject Hermann Hoth E11239 entity
Predicate givenName P17 FINISHED
Object Hermann E24628 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 | Statement: [Hermann Hoth, givenName, Hermann]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Hermann
Context triple: [Hermann Hoth, givenName, Hermann]
  • A. Hermann chosen
    Hermann Minkowski was a German mathematician best known for developing the geometric formulation of special relativity using four-dimensional spacetime.
  • B. Wilhelm
    Wilhelm is a Germanic given name, equivalent to William, historically borne by numerous European nobles, rulers, and notable figures.
  • C. Helmut
    Helmut is a masculine given name of German origin, historically common in German-speaking countries.
  • D. Heinrich
    Heinrich is a masculine given name of German origin that has been borne by numerous historical figures, including nobility, scholars, and political leaders.
  • E. Erwin
    Erwin is a masculine given name of German origin, historically associated with figures such as the World War II field marshal Erwin Rommel.
  • 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_69a493266a2881909daf4c40f719dee8 completed March 1, 2026, 7:27 p.m.
NER Named-entity recognition batch_69a49f1b24b08190897d8aedb877bd83 completed March 1, 2026, 8:18 p.m.
NED1 Entity disambiguation (via context triple) batch_69a66665071481909720020659ef60ab completed March 3, 2026, 4:41 a.m.
Created at: March 1, 2026, 7:36 p.m.