Triple

T23395852
Position Surface form Disambiguated ID Type / Status
Subject Böhm E559355 entity
Predicate hasVariant P455 FINISHED
Object Boehm 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: Boehm | Statement: [Böhm, hasVariant, Boehm]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Boehm
Context triple: [Böhm, hasVariant, Boehm]
  • A. Boehm chosen
    Boehm is a surname most prominently associated with Barry W. Boehm, an influential American software engineer known for his work on software cost estimation and the Spiral Model of software development.
  • B. Boyer
    Boyer is a surname most notably associated with Herbert Boyer, a pioneering biochemist and co-founder of the biotechnology company Genentech.
  • C. Dekker
    Dekker is a Dutch-origin surname borne by various notable individuals across fields such as literature, sports, and entertainment.
  • D. Bonger
    Bonger is a Dutch surname most notably associated with Johanna van Gogh-Bonger, the key figure in preserving and promoting Vincent van Gogh’s artistic legacy.
  • E. Backus
    Backus is a surname most notably associated with John Backus, the American computer scientist who led the development of the Fortran programming language.
  • 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_69e24549610c8190a069d6411ce5f661 completed April 17, 2026, 2:35 p.m.
NER Named-entity recognition batch_69f1a4db1c888190ace5d58bcc8645c1 completed April 29, 2026, 6:27 a.m.
Created at: April 17, 2026, 5:36 p.m.