Triple

T17839763
Position Surface form Disambiguated ID Type / Status
Subject Karl Wilhelm von Heideck E445491 entity
Predicate familyName P18 FINISHED
Object von Heideck NE NERFINISHED

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: von Heideck | Statement: [Karl Wilhelm von Heideck, familyName, von Heideck]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: von Heideck
Context triple: [Karl Wilhelm von Heideck, familyName, von Heideck]
  • A. Heideck chosen
    Heideck was a notable Philhellene, remembered for his support of the Greek cause during the Greek War of Independence.
  • B. von Bock
    Von Bock is a German noble surname most prominently associated with Fedor von Bock, a senior Wehrmacht field marshal during World War II.
  • C. Iron Heinrich
    Iron Heinrich is a loyal servant in the fairy tale "The Frog Prince," known for the iron bands he wears around his heart to keep it from breaking over his master's misfortune.
  • D. Oscar Werwath
    Oscar Werwath was a German-born American engineer and educator best known as the founder and first leader of the Milwaukee School of Engineering.
  • E. Helmuth
    Helmuth is a masculine given name of German origin, historically borne by several notable military and political figures.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69d8b9f1a6d881909f024bc603111cdb completed April 10, 2026, 8:50 a.m.
NER Named-entity recognition batch_69e48d2a570c81909787296bde7e795c completed April 19, 2026, 8:07 a.m.
Created at: April 10, 2026, 10:16 a.m.