Triple
T31661496
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Julius von Haast |
E808013
|
entity |
| Predicate | notableEponym |
P174613
|
FINISHED |
| Object | Haast Pass |
E616481
|
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: Haast Pass | Statement: [Julius von Haast, notableEponym, Haast Pass]
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 (4 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_69f348dbeef4819080b446a7feb6340b |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2b84b0ca388190bdc871911c3602bb |
completed | June 12, 2026, 4:01 a.m. |
| PD | Predicate disambiguation | batch_6a0379e7aa0c8190bdc9ee4d54fc821b |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 30, 2026, 10:57 p.m.