Triple
T8374948
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Helmuth Weidling |
E197552
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Weidling |
E197552
|
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: Weidling | Statement: [Helmuth Weidling, familyName, Weidling]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Weidling Context triple: [Helmuth Weidling, familyName, Weidling]
-
A.
Weidling
chosen
Weidling is a German surname most notably associated with General Helmuth Weidling, the last commander of Berlin’s defenses in World War II.
-
B.
Marchfeld
Marchfeld is a fertile lowland region in eastern Austria known for its intensive agriculture and vegetable production.
-
C.
Eidlitz
Eidlitz is a surname most notably associated with Leopold Eidlitz, a prominent 19th-century American architect.
-
D.
Seckbach
Seckbach is a district in the east of Frankfurt am Main, Germany, known for its residential character and proximity to green spaces like the Lohrberg.
-
E.
Paplitz
Paplitz is a village and local subdivision of the town of Genthin in the German state of Saxony-Anhalt.
- 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_69ca82f56730819080cec5d991c76f4c |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb80a996ec819083ce2607c0cdab7f |
completed | March 31, 2026, 8:07 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ce1d14baf88190bc260efda7d0fc0d |
completed | April 2, 2026, 7:39 a.m. |
Created at: March 30, 2026, 6:01 p.m.