Triple

T16716108
Position Surface form Disambiguated ID Type / Status
Subject Walter Kasper E406229 entity
Predicate familyName P18 FINISHED
Object Kasper E875537 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: Kasper | Statement: [Walter Kasper, familyName, Kasper]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Kasper
Context triple: [Walter Kasper, familyName, Kasper]
  • A. Kasper chosen
    Kasper is a surname most notably associated with former American football wide receiver Kevin Kasper.
  • B. Kaspar
    Kaspar is a 1967 play by Austrian writer Peter Handke that explores language, identity, and social conditioning through the story of a speechless outsider molded by external voices.
  • C. Jesper
    Jesper is a masculine given name commonly used in Scandinavian countries and parts of Europe.
  • D. Caspar
    Caspar is one of the Three Wise Men in Christian tradition, often depicted as a king who visited the infant Jesus bearing gifts.
  • E. Johan
    Johan is the given first name of J. Erik Jonsson, an American businessman and philanthropist who co-founded Texas Instruments and served as mayor of Dallas.
  • 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_69d8838f242881908abd8bc138795886 completed April 10, 2026, 4:58 a.m.
NER Named-entity recognition batch_69e38655b54c81908c2cf7b42df996a4 completed April 18, 2026, 1:25 p.m.
NED1 Entity disambiguation (via context triple) batch_6a0091ab9e54819097e71ce1616b28b5 completed May 10, 2026, 2:09 p.m.
Created at: April 10, 2026, 5:20 a.m.