Triple
T17604777
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ernst Vanselow |
E428797
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Vanselow |
—
|
NE NERFINISHED |
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: Vanselow | Statement: [Ernst Vanselow, familyName, Vanselow]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Vanselow Context triple: [Ernst Vanselow, familyName, Vanselow]
-
A.
Vanselow
chosen
Vanselow is a German-language surname borne by various individuals, including figures such as Ernst Vanselow.
-
B.
Eickeloh
Eickeloh is a small municipality in Lower Saxony, Germany, situated in the Heidekreis district.
-
C.
Hollenbach
Hollenbach is a small municipality in the district of Aichach-Friedberg in the Bavarian region of Germany.
-
D.
Schermerhorne
Schermerhorne is a variant spelling of the Dutch surname Schermerhorn, which is associated with a historic family name and several notable places and individuals.
-
E.
Weitzel
Weitzel is a surname of likely German or Dutch origin borne by individuals such as Edu Weitzel Douwes Dekker.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d889e1c6148190ba76241e74688f8b |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e46c4b4ee88190827ea28b99ca6f33 |
completed | April 19, 2026, 5:46 a.m. |
Created at: April 10, 2026, 5:51 a.m.