Triple
T7977986
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Levin August von Bennigsen |
E185494
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | von Bennigsen |
E185494
|
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: von Bennigsen | Statement: [Levin August von Bennigsen, familyName, von Bennigsen]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: von Bennigsen Context triple: [Levin August von Bennigsen, familyName, von Bennigsen]
-
A.
Bennigsen
chosen
Bennigsen was a Russian general best known for leading the Imperial Russian Army against Napoleon during the Napoleonic Wars.
-
B.
von Bock
Von Bock is a German noble surname most prominently associated with Fedor von Bock, a senior Wehrmacht field marshal during World War II.
-
C.
von Kluck
Von Kluck is a German noble family name most notably borne by Alexander von Kluck, a Prussian general who played a key role in the early battles of World War I.
-
D.
von Frundsberg
von Frundsberg is the noble German family name associated with the renowned 16th-century Landsknecht commander Georg von Frundsberg.
-
E.
Schörner
Schörner is a German surname most notably borne by Ferdinand Schörner, a high-ranking Wehrmacht field marshal during World War II.
- 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_69ca829851908190b4e03829353ee7c3 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3bf84b1081908e60a556d984aad6 |
completed | March 31, 2026, 3:14 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cbe0cc09a081909cb92cd4864ef50d |
completed | March 31, 2026, 2:57 p.m. |
Created at: March 30, 2026, 5:14 p.m.