Triple
T20728031
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hendrik Willem Burger |
E509489
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Hendrik |
—
|
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: Hendrik | Statement: [Hendrik Willem Burger, givenName, Hendrik]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Hendrik Context triple: [Hendrik Willem Burger, givenName, Hendrik]
-
A.
Hendrik
chosen
Hendrik is a masculine given name of Germanic origin, commonly used in Dutch- and German-speaking countries and related to the name Henry.
-
B.
Willem
Willem is a given name, primarily used in Dutch-speaking regions, that corresponds to the English name William.
-
C.
Diederik
Diederik is a masculine given name of Dutch origin, notably borne by Dutch politician Diederik Samsom.
-
D.
Adriaan
Adriaan is a masculine given name of Dutch origin commonly used in the Netherlands and other Dutch-speaking regions.
-
E.
Hendrieken
Hendrieken is a village that forms one of the municipal sections of Borgloon in the Belgian province of Limburg.
- 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_69e0b4c4cc648190b45fda6e2b20af56 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c1e9ed708190ad8e371646630fea |
completed | April 21, 2026, 12:16 a.m. |
Created at: April 16, 2026, 12:30 p.m.