Triple

T18202244
Position Surface form Disambiguated ID Type / Status
Subject Alexander Kluge E435817 entity
Predicate familyName P18 FINISHED
Object Kluge 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: Kluge | Statement: [Alexander Kluge, familyName, Kluge]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Kluge
Context triple: [Alexander Kluge, familyName, Kluge]
  • A. Kluge chosen
    Kluge is a German surname borne by several notable figures, including military leaders, scholars, and public personalities.
  • B. Klug
    Klug is a surname most notably associated with Aaron Klug, the Nobel Prize–winning chemist and biophysicist known for his work on crystallographic electron microscopy.
  • C. Cleverly
    Cleverly is a Welsh surname most notably associated with former world light-heavyweight boxing champion Nathan Cleverly.
  • D. the Brilliant
    The Brilliant was the epithet of George V of Georgia, a 14th-century king renowned for restoring and strengthening the Georgian kingdom after a period of decline.
  • E. Klausi
    Klausi is a German diminutive form of the male given name Klaus, often used as an affectionate nickname.
  • 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_69d8b90dba6481908e119eb9aa4ca0cb completed April 10, 2026, 8:47 a.m.
NER Named-entity recognition batch_69e4e220dca48190b54dabbd3c7c99b7 completed April 19, 2026, 2:09 p.m.
Created at: April 10, 2026, 10:32 a.m.