Triple
T8365534
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Helmut Weinert |
E197115
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Weinert |
E197115
|
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: Weinert | Statement: [Helmut Weinert, familyName, Weinert]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Weinert Context triple: [Helmut Weinert, familyName, Weinert]
-
A.
Weinert
chosen
Weinert is a German-language surname borne by various notable individuals in fields such as the arts, sciences, and public life.
-
B.
Braunshardt
Braunshardt is a district of the town of Weiterstadt in the state of Hesse, Germany.
-
C.
Weitzel
Weitzel is a surname of likely German or Dutch origin borne by individuals such as Edu Weitzel Douwes Dekker.
-
D.
Heurich
Heurich is a German surname most notably associated with Christian Heurich, a prominent brewer and businessman in Washington, D.C.
-
E.
Seelbach
Seelbach is a municipality in southwestern Germany’s Baden-Württemberg region, situated in the Ortenau district near the Black Forest.
- 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_69ca82f2dbe48190aba982e75a0d94de |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb808bc22481909ce2f8b48cc95806 |
completed | March 31, 2026, 8:06 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cebb37161081908452cc449b4e903e |
completed | April 2, 2026, 6:53 p.m. |
Created at: March 30, 2026, 6 p.m.