Triple
T707043
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gerhard Klopfer |
E14123
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Gerhard |
E54950
|
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: Gerhard | Statement: [Gerhard Klopfer, givenName, Gerhard]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Gerhard Context triple: [Gerhard Klopfer, givenName, Gerhard]
-
A.
Gerhard
chosen
Gerhard is a masculine given name of German origin, historically common in German-speaking countries.
-
B.
Wilhelm
Wilhelm is a Germanic given name, equivalent to William, historically borne by numerous European nobles, rulers, and notable figures.
-
C.
Nikolaus
Nikolaus is the traditional German figure based on Saint Nicholas who brings small gifts to children on the eve of December 6th.
-
D.
Theodor
Theodor "Ted" Nelson is an American pioneer of information technology best known for coining the term "hypertext" and envisioning global hyperlinked document systems.
-
E.
Helmut
Helmut is a masculine given name of German origin, historically common in German-speaking countries.
- 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_69a493494ec48190ae6751683625a9ba |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a5477bb48190a2032edc83a24720 |
completed | March 1, 2026, 8:44 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69a7cf4b62b08190bc8d5978595ce60b |
completed | March 4, 2026, 6:20 a.m. |
Created at: March 1, 2026, 7:36 p.m.