Triple
T20937957
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rüdiger von der Goltz |
E515635
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Rüdiger |
—
|
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: Rüdiger | Statement: [Rüdiger von der Goltz, givenName, Rüdiger]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Rüdiger Context triple: [Rüdiger von der Goltz, givenName, Rüdiger]
-
A.
Rüdiger
chosen
Rüdiger is a German given name of Germanic origin, commonly used as a masculine first name in German-speaking countries.
-
B.
Wolf Rüdiger
Wolf Rüdiger was a German architect and author best known as the son of Rudolf Hess and for his controversial efforts to rehabilitate his father's reputation.
-
C.
Rudi Jäger
Rudi Jäger is a sadistic Nazi prison warden and antagonist in the video game Wolfenstein: The Old Blood, known for hunting the protagonist with his attack dogs.
-
D.
Reinhard
Reinhard is a masculine German given name historically borne by several notable figures, including high-ranking officials in Nazi Germany.
-
E.
Jürgen
Jürgen is a masculine given name of German origin, commonly used in German-speaking countries.
- 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_69e0b4fc13408190b06868df03c5c29b |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6f9534cd48190a86665fb1df6b077 |
completed | April 21, 2026, 4:13 a.m. |
Created at: April 16, 2026, 12:50 p.m.