Triple
T22660803
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Johanna Gezina Bonger |
E559655
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Bonger |
—
|
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: Bonger | Statement: [Johanna Gezina Bonger, familyName, Bonger]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Bonger Context triple: [Johanna Gezina Bonger, familyName, Bonger]
-
A.
Bonger
chosen
Bonger is a Dutch surname most notably associated with Johanna van Gogh-Bonger, the key figure in preserving and promoting Vincent van Gogh’s artistic legacy.
-
B.
Bouhler
Bouhler is a German surname most notably associated with Philipp Bouhler, a high-ranking Nazi official and close associate of Adolf Hitler.
-
C.
Oberholtzer
Oberholtzer is a German-origin surname, often associated with Mennonite and Amish families, that serves as a variant of the Overholt family name.
-
D.
Burgon
Burgon is an English surname most notably associated with composer Geoffrey Burgon.
-
E.
Boulger
Boulger is a surname, likely a variant spelling of Bulger, borne by various individuals of Irish or British origin.
- 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_69e2454a158c819093b8e35f5045efb6 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f1765edf88819086c28525e3c73758 |
completed | April 29, 2026, 3:09 a.m. |
Created at: April 17, 2026, 3:07 p.m.