Triple
T4070625
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gerhard Klopfer |
E86636
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Klopfer |
E86636
|
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: Klopfer | Statement: [Gerhard Klopfer, familyName, Klopfer]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Klopfer Context triple: [Gerhard Klopfer, familyName, Klopfer]
-
A.
Klopfer
chosen
Klopfer is a German surname most notably associated with Gerhard Klopfer, a Nazi official involved in high-level administrative functions during the Third Reich.
-
B.
Hölldobler
Hölldobler is a German surname most notably associated with Bert Hölldobler, a prominent behavioral ecologist and myrmecologist known for his research on ants.
-
C.
Körner
Körner is a German surname borne by various notable figures in fields such as literature, music, and politics.
-
D.
Klecko
Klecko is the surname of former American football defensive lineman Joe Klecko, best known for his standout career with the New York Jets as part of the “New York Sack Exchange.”
-
E.
Bittrich
Bittrich is a German surname most notably borne by Wilhelm Bittrich, a high-ranking Waffen-SS commander 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_69aed93ebe448190a1f1686e28740ac9 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefc1f6d9c8190845d2fcd15fcdfd6 |
completed | March 9, 2026, 4:58 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b562b6eb708190a7f60192d8df9a27 |
completed | March 14, 2026, 1:29 p.m. |
Created at: March 9, 2026, 3:38 p.m.