Triple
T18793269
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Diederik Johannes Korteweg |
E459569
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Diederik |
—
|
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: Diederik | Statement: [Diederik Johannes Korteweg, givenName, Diederik]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Diederik Context triple: [Diederik Johannes Korteweg, givenName, Diederik]
-
A.
Diederik
chosen
Diederik is a masculine given name of Dutch origin, notably borne by Dutch politician Diederik Samsom.
-
B.
Zederik
Zederik was a former municipality in the Dutch province of South Holland that was incorporated into the new municipality of Vijfheerenlanden.
-
C.
Adriaan
Adriaan is a masculine given name of Dutch origin commonly used in the Netherlands and other Dutch-speaking regions.
-
D.
Hendrik
Hendrik is a masculine given name of Germanic origin, commonly used in Dutch- and German-speaking countries and related to the name Henry.
-
E.
Willem
Willem is a given name, primarily used in Dutch-speaking regions, that corresponds to the English name William.
- 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_69d8d396f54c8190ba49db31e8743842 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e59787e5988190883ed575ab4b6dec |
completed | April 20, 2026, 3:03 a.m. |
Created at: April 10, 2026, 11:53 a.m.