Triple

T14971538
Position Surface form Disambiguated ID Type / Status
Subject Wilhelm Heinrich Otto Dix E373331 entity
Predicate hasFamilyName P18 FINISHED
Object Dix E44373 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: Dix | Statement: [Wilhelm Heinrich Otto Dix, hasFamilyName, Dix]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Dix
Context triple: [Wilhelm Heinrich Otto Dix, hasFamilyName, Dix]
  • A. Dix chosen
    Dix is the surname of Dorothea Dix, the 19th-century American social reformer known for her pioneering work in mental health care and prison reform.
  • B. Dixon
    Dixon is an alternative name for Dikson, a remote Arctic settlement and port in northern Russia.
  • C. Dixon
    Dixon is a small agricultural city in Northern California known historically for sheep ranching and its annual May Fair.
  • D. Villard
    Villard is a surname most notably associated with Oswald Garrison Villard, an American journalist and civil rights activist.
  • E. Choulex
    Choulex is a small municipality in the canton of Geneva in southwestern Switzerland, known for its rural character and proximity to the city of Geneva.
  • 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_69d85ccbbcd48190acb56e7cf104d8ad completed April 10, 2026, 2:13 a.m.
NER Named-entity recognition batch_69ded6e59a7c8190a1634a706ea68fda completed April 15, 2026, 12:08 a.m.
NED1 Entity disambiguation (via context triple) batch_69fe8be8af688190832efb00695f8b20 completed May 9, 2026, 1:20 a.m.
Created at: April 10, 2026, 2:50 a.m.