Triple
T4770530
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wüthrich |
E105915
|
entity |
| Predicate | hasNotableBearer |
P458
|
FINISHED |
| Object |
Daniel Wüthrich
Daniel Wüthrich is a notable individual who bears the surname Wüthrich, recognized enough to be specifically cited as an example of this family name.
|
E485737
|
NE FINISHED |
How this triple was built (4 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: Daniel Wüthrich | Statement: [Wüthrich, hasNotableBearer, Daniel Wüthrich]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Daniel Wüthrich Context triple: [Wüthrich, hasNotableBearer, Daniel Wüthrich]
-
A.
Martin Wüthrich
Martin Wüthrich is a notable individual who carries the surname Wüthrich, recognized as a distinguished bearer of this family name.
-
B.
Markus Wüthrich
Markus Wüthrich is a notable individual who bears the surname Wüthrich, recognized enough to be specifically cited among its prominent holders.
-
C.
Thomas Wüthrich
Thomas Wüthrich is a person notable enough to be specifically cited as a bearer of the surname Wüthrich.
-
D.
Bruno Wüthrich
Bruno Wüthrich is an individual notable enough to be recognized as a prominent bearer of the surname Wüthrich.
-
E.
Sandro Wüthrich
Sandro Wüthrich is an individual notable enough to be recognized as a namesake of the surname Wüthrich.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Daniel Wüthrich Triple: [Wüthrich, hasNotableBearer, Daniel Wüthrich]
Generated description
Daniel Wüthrich is a notable individual who bears the surname Wüthrich, recognized enough to be specifically cited as an example of this family name.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Daniel Wüthrich Target entity description: Daniel Wüthrich is a notable individual who bears the surname Wüthrich, recognized enough to be specifically cited as an example of this family name.
-
A.
Martin Wüthrich
Martin Wüthrich is a notable individual who carries the surname Wüthrich, recognized as a distinguished bearer of this family name.
-
B.
Markus Wüthrich
Markus Wüthrich is a notable individual who bears the surname Wüthrich, recognized enough to be specifically cited among its prominent holders.
-
C.
Thomas Wüthrich
Thomas Wüthrich is a person notable enough to be specifically cited as a bearer of the surname Wüthrich.
-
D.
Bruno Wüthrich
Bruno Wüthrich is an individual notable enough to be recognized as a prominent bearer of the surname Wüthrich.
-
E.
Sandro Wüthrich
Sandro Wüthrich is an individual notable enough to be recognized as a namesake of the surname Wüthrich.
- F. None of above. chosen
Provenance (5 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_69be922efb7c8190a7ea9a7c9aa5503d |
completed | March 21, 2026, 12:42 p.m. |
| NEDg | Description generation | batch_69be92976ee081909bfd282c17db1612 |
completed | March 21, 2026, 12:44 p.m. |
| NED2 | Entity disambiguation (via description) | batch_69be930bc19c8190a2c4716df41446d6 |
completed | March 21, 2026, 12:46 p.m. |
Created at: March 20, 2026, 1:21 p.m.