Triple

T12677913
Position Surface form Disambiguated ID Type / Status
Subject Klaus Schütz E302866 entity
Predicate familyName P18 FINISHED
Object Schütz E556747 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: Schütz | Statement: [Klaus Schütz, familyName, Schütz]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Schütz
Context triple: [Klaus Schütz, familyName, Schütz]
  • A. Schütz chosen
    Schütz is a German surname most famously associated with Heinrich Schütz, a prominent early Baroque composer.
  • B. Johann Hermann Schein
    Johann Hermann Schein was a prominent early Baroque German composer and cantor, known for his sacred and secular vocal music and his influential role in Leipzig’s musical life.
  • C. Franz von Walsegg
    Franz von Walsegg was an Austrian count and amateur musician best known for anonymously commissioning Mozart’s Requiem, which he intended to pass off as his own composition.
  • D. Clemens Holzmeister
    Clemens Holzmeister was a prominent Austrian architect known for his monumental public buildings and influential role in 20th-century European architecture.
  • E. Johann Brechtel
    Johann Brechtel was a notable historical figure from the German town of Weil der Stadt, recognized for his local significance.
  • 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_69d7bdee64a08190801c6d470aefd723 completed April 9, 2026, 2:55 p.m.
NER Named-entity recognition batch_69d961b1dff48190923290555ece5d89 completed April 10, 2026, 8:46 p.m.
NED1 Entity disambiguation (via context triple) batch_69f671a341288190822fae2469efea09 completed May 2, 2026, 9:50 p.m.
Created at: April 9, 2026, 5:20 p.m.