Triple
T2878146
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Günther von Kluge |
E56928
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Günther |
E172627
|
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: Günther | Statement: [Günther von Kluge, givenName, Günther]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Günther Context triple: [Günther von Kluge, givenName, Günther]
-
A.
Günther
chosen
Günther is a German masculine given name traditionally associated with figures of Germanic origin and culture.
-
B.
Othmar
Othmar is a masculine given name of Germanic origin, notably borne by the Swiss-American civil engineer Othmar Ammann.
-
C.
Hermann
Hermann Minkowski was a German mathematician best known for developing the geometric formulation of special relativity using four-dimensional spacetime.
-
D.
Hermann
Hermann is a German surname borne by various notable individuals across fields such as philosophy, science, and the arts.
-
E.
Ernst
Ernst is a masculine given name of Germanic origin, commonly used in German-speaking and Scandinavian countries.
- 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_69ab4a4ced288190ab6d3e062d10f7f6 |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abe008925c81909683d0ebc6227e5e |
completed | March 7, 2026, 8:21 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b354505574819083ae7d36e461366b |
completed | March 13, 2026, 12:03 a.m. |
Created at: March 6, 2026, 10:03 p.m.