Triple
T4305105
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ernst Vanselow |
E99935
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Ernst |
E81465
|
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: Ernst | Statement: [Ernst Vanselow, givenName, Ernst]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ernst Context triple: [Ernst Vanselow, givenName, Ernst]
-
A.
Ernst
chosen
Ernst is a masculine given name of Germanic origin, commonly used in German-speaking and Scandinavian countries.
-
B.
Günther
Günther is a German masculine given name traditionally associated with figures of Germanic origin and culture.
-
C.
Erwin
Erwin is a masculine given name of German origin, historically associated with figures such as the World War II field marshal Erwin Rommel.
-
D.
Hermann
Hermann Minkowski was a German mathematician best known for developing the geometric formulation of special relativity using four-dimensional spacetime.
-
E.
Hermann
Hermann is a German surname borne by various notable individuals across fields such as philosophy, science, and the arts.
- 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_69b345528ebc8190b5abc7e95094792d |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b350b8e1cc819094ce3d6f6c8da767 |
completed | March 12, 2026, 11:48 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b5f5bf4dd48190b84d8488a4f196a8 |
completed | March 14, 2026, 11:56 p.m. |
Created at: March 12, 2026, 11:09 p.m.