Triple

T22519972
Position Surface form Disambiguated ID Type / Status
Subject Schütz E556747 entity
Predicate hasVariant P455 FINISHED
Object Schutz 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: Schutz | Statement: [Schütz, hasVariant, Schutz]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Schutz
Context triple: [Schütz, hasVariant, Schutz]
  • A. Schutz chosen
    Schutz is a variant spelling of the surname Schultz, commonly of German origin.
  • B. Nebelschütz
    Nebelschütz is a small municipality in eastern Saxony, Germany, known for its Sorbian cultural heritage and rural setting.
  • C. Scheuer
    Scheuer is a German-origin surname borne by various notable individuals in politics, academia, and other fields.
  • D. Schonungen
    Schonungen is a municipality in the Lower Franconia region of Bavaria, Germany, situated near the city of Schweinfurt along the Main River.
  • E. Schutter
    The Schutter is a river in southwestern Germany that flows through the state of Baden-Württemberg and is a tributary of the Kinzig.
  • 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_69e11e5657e881909f16ca58352c50da completed April 16, 2026, 5:37 p.m.
NER Named-entity recognition batch_69f15e31f43c8190899f5e35b150fe85 completed April 29, 2026, 1:26 a.m.
Created at: April 16, 2026, 8:50 p.m.