Triple

T21828034
Position Surface form Disambiguated ID Type / Status
Subject Johann Weiss E538906 entity
Predicate hasGivenName P17 FINISHED
Object Johann 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: Johann | Statement: [Johann Weiss, hasGivenName, Johann]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Johann
Context triple: [Johann Weiss, hasGivenName, Johann]
  • A. Johann chosen
    Johann is a given name of Germanic origin commonly used in German-speaking and other European countries.
  • B. Johannes
    Johannes is the given first name of Hubertus van Mook, a Dutch colonial administrator who served as Governor-General of the Dutch East Indies during and after World War II.
  • C. Johannes
    Johannes is a masculine given name of Hebrew origin, related to names like John and Johan and common in various European languages.
  • D. Johannes
    Johannes is the given first name of the German nuclear physicist Hans D. Jensen, a Nobel Prize laureate in Physics.
  • E. Johannes
    Johannes is the given name of Frederik Johannes Willem Reitz, a prominent South African lawyer, politician, and former State President of the Orange Free State.
  • 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_69e0c475038c8190abb9b1a20eb8ff50 completed April 16, 2026, 11:13 a.m.
NER Named-entity recognition batch_69f09133718081909faa67c3721aed52 completed April 28, 2026, 10:51 a.m.
Created at: April 16, 2026, 6:54 p.m.