Triple
T26238156
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Franz Xaver Rudolf von Höhnel |
E656228
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Austrian mycologist |
C10719
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: Austrian mycologist Context triple: [Franz Xaver Rudolf von Höhnel, instanceOf, Austrian mycologist]
-
A.
Austrian scientist
chosen
An Austrian scientist is a researcher originating from or working primarily in Austria who systematically investigates natural or formal phenomena to expand scientific knowledge.
-
B.
Austrian-American scientist
An Austrian-American scientist is a researcher or academic originally from Austria who became a U.S. citizen or resident and contributed to scientific advancement through work conducted in both cultural and national contexts.
-
C.
Hungarian scientist
A Hungarian scientist is a researcher originating from or working in Hungary who contributes to scientific knowledge through systematic investigation and experimentation in their field of expertise.
-
D.
Czech scientist
A Czech scientist is a professional researcher originating from or working in the Czech Republic who systematically investigates natural, social, or formal phenomena to expand knowledge and develop practical applications.
-
E.
scientist from the Habsburg Netherlands
A scientist from the Habsburg Netherlands is a natural philosopher, mathematician, or empirical investigator who lived and worked in the Low Countries under Habsburg rule, contributing to early modern European scientific thought and practice.
- F. None of above.
Provenance (1 batch)
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_69ee5b4c59a881909d9ee4fd013fffd5 |
completed | April 26, 2026, 6:37 p.m. |
Created at: April 26, 2026, 9:02 p.m.