Triple
T31661496
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Julius von Haast |
E808013
|
entity |
| Predicate | notableEponym |
—
|
GENERATED |
| Object | Haast Pass |
—
|
UNRECOGNIZED GENERATED |
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableEponym Context triple: [Julius von Haast, notableEponym, Haast Pass]
-
A.
eponymKnownFor
Indicates that a person or entity is widely recognized or named as the source or inspiration for something else (such as a concept, place, or object).
-
B.
eponymProfession
Indicates that a person’s profession is the source of an eponym, i.e., a word or name derived from that professional role.
-
C.
namedPersonNotableFor
Indicates that a person is especially known or recognized for a particular work, role, achievement, or characteristic.
-
D.
fieldOfEponym
Indicates the domain, discipline, or area of activity in which an eponymous name (e.g., a person or thing something is named after) is recognized or relevant.
-
E.
hasEponymNotability
chosen
Indicates that an entity is notable specifically for having something (such as a place, object, or concept) named after it.
- 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_69f348dbeef4819080b446a7feb6340b |
completed | April 30, 2026, 12:19 p.m. |
Created at: April 30, 2026, 10:57 p.m.