Triple

T3685907
Position Surface form Disambiguated ID Type / Status
Subject Duke Henry of Mecklenburg-Schwerin E78223 entity
Predicate givenName P17 FINISHED
Object Heinrich E70531 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: Heinrich | Statement: [Duke Henry of Mecklenburg-Schwerin, givenName, Heinrich]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Heinrich
Context triple: [Duke Henry of Mecklenburg-Schwerin, givenName, Heinrich]
  • A. Heinrich chosen
    Heinrich is a masculine given name of German origin that has been borne by numerous historical figures, including nobility, scholars, and political leaders.
  • B. Hermann
    Hermann Minkowski was a German mathematician best known for developing the geometric formulation of special relativity using four-dimensional spacetime.
  • C. Hermann
    Hermann is a German surname borne by various notable individuals across fields such as philosophy, science, and the arts.
  • D. Günther
    Günther is a German masculine given name traditionally associated with figures of Germanic origin and culture.
  • E. Gustav
    Gustav is a masculine given name of German origin, borne by several notable historical figures including scientists, artists, and royalty.
  • 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_69ad85e285a081908f8cbfa9e2ed9b75 completed March 8, 2026, 2:21 p.m.
NER Named-entity recognition batch_69adc4c676748190b074abfb9ba43b49 completed March 8, 2026, 6:49 p.m.
NED1 Entity disambiguation (via context triple) batch_69b4c3bd473c8190b814689f3c76cada completed March 14, 2026, 2:11 a.m.
Created at: March 8, 2026, 3:26 p.m.