Triple
T18125702
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Klaus Hamm-Brücher |
E433868
|
entity |
| Predicate | hasFamilyName |
P18
|
FINISHED |
| Object | Hamm-Brücher |
—
|
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: Hamm-Brücher | Statement: [Klaus Hamm-Brücher, hasFamilyName, Hamm-Brücher]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Hamm-Brücher Context triple: [Klaus Hamm-Brücher, hasFamilyName, Hamm-Brücher]
-
A.
Hamm-Brücher
chosen
Hamm-Brücher is the hyphenated surname associated with German politician and liberal education advocate Hildegard Hamm-Brücher.
-
B.
Hammann
Hammann is a German-origin surname borne by various notable individuals in fields such as aviation, music, and academia.
-
C.
Hücker-Aschen
Hücker-Aschen is a village-level district within the town of Spenge in North Rhine-Westphalia, Germany.
-
D.
Hauerland
Hauerland was a historical German-speaking enclave in central Slovakia, settled by Carpathian Germans in the Middle Ages.
-
E.
Stöcker
Stöcker is a German surname that is a variant of the name Stoker.
- 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_69d8b909e8cc81908df4cc2b8ea6d11f |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4ddee1efc8190b04324b98de5c9d0 |
completed | April 19, 2026, 1:51 p.m. |
Created at: April 10, 2026, 10:29 a.m.