Triple
T16445408
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Friedrich von Wieser |
E399410
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Wieser |
E399410
|
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: Wieser | Statement: [Friedrich von Wieser, familyName, Wieser]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Wieser Context triple: [Friedrich von Wieser, familyName, Wieser]
-
A.
Wieser
chosen
Wieser is a German-language surname most notably associated with Austrian economist Friedrich von Wieser, a key figure of the Austrian School of economics.
-
B.
Wirth
Wirth is a Swiss surname most notably associated with computer scientist Niklaus Wirth, the designer of several influential programming languages.
-
C.
Paepcke
Paepcke is a surname most notably associated with Walter Paepcke, the American industrialist and cultural philanthropist who founded the Aspen Institute.
-
D.
Eberl
Eberl is a German-language surname of Austrian and Bavarian origin borne by various notable individuals.
-
E.
Rutishauser
Rutishauser is a Swiss surname most notably associated with Heinz Rutishauser, a pioneering mathematician and computer scientist in the field of numerical analysis and early programming languages.
- 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_69d87f2c6778819080fcfae53be8f12a |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e32cdb5d908190bb6c5cb3c794cf4b |
completed | April 18, 2026, 7:03 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a0045922d748190bb3200c96f244149 |
completed | May 10, 2026, 8:45 a.m. |
Created at: April 10, 2026, 5:10 a.m.