Triple

T18150506
Position Surface form Disambiguated ID Type / Status
Subject Johann Speer E434487 entity
Predicate nameInLatinAlphabet P22444 FINISHED
Object Johann Speer 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 Speer | Statement: [Johann Speer, nameInLatinAlphabet, Johann Speer]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Johann Speer
Context triple: [Johann Speer, nameInLatinAlphabet, Johann Speer]
  • A. Johann Speer chosen
    Johann Speer is a person notable enough to be recognized as a bearer of the surname Speer, though specific widely known biographical details about him are not clearly established.
  • B. Ludwig Speer
    Ludwig Speer is a notable individual who shares the Speer surname, recognized as a distinct bearer of this family name.
  • C. Reinhard Speer
    Reinhard Speer is a relatively obscure individual known primarily from name-bearing records rather than for widely documented public achievements.
  • D. Heinrich Speer
    Heinrich Speer is a relatively obscure historical figure known primarily through records that list him as a notable bearer of the surname Speer.
  • E. Thomas Speer
    Thomas Speer is an individual notable enough to be recognized as a prominent bearer of the surname Speer.
  • 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_69d8b90aac308190801e2c57d8c5bfe5 completed April 10, 2026, 8:47 a.m.
NER Named-entity recognition batch_69e4de3812e8819097f025476d5c6a1d completed April 19, 2026, 1:52 p.m.
Created at: April 10, 2026, 10:29 a.m.