Triple
T4770536
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kurt Wüthrich |
E105915
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Wüthrich |
E105915
|
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: Wüthrich | Statement: [Kurt Wüthrich, familyName, Wüthrich]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Wüthrich Context triple: [Kurt Wüthrich, familyName, Wüthrich]
-
A.
Wüthrich
chosen
Wüthrich is a Swiss surname most notably associated with Nobel Prize–winning chemist Kurt Wüthrich.
-
B.
Wehrli
Wehrli is a surname most notably associated with Roger Wehrli, a Hall of Fame American football cornerback who played for the St. Louis Cardinals.
-
C.
Wirth
Wirth is a Swiss surname most notably associated with computer scientist Niklaus Wirth, the designer of several influential programming languages.
-
D.
Huldrych
Huldrych is the given name of Huldrych Zwingli, the influential Swiss reformer and key figure in the early Protestant Reformation.
-
E.
Othmar
Othmar is a masculine given name of Germanic origin, notably borne by the Swiss-American civil engineer Othmar Ammann.
- 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_69bd43f226fc8190b867cc249c2a9042 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd655c9a2c8190adce3e2a8a1fa0a7 |
completed | March 20, 2026, 3:18 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69be3a94e340819080fe92a2024abdaf |
completed | March 21, 2026, 6:28 a.m. |
Created at: March 20, 2026, 1:21 p.m.