Triple
T11866246
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hendrikus Colijn |
E282291
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Hendrikus |
E104689
|
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: Hendrikus | Statement: [Hendrikus Colijn, givenName, Hendrikus]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Hendrikus Context triple: [Hendrikus Colijn, givenName, Hendrikus]
-
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.
Adriaan
Adriaan is a masculine given name of Dutch origin commonly used in the Netherlands and other Dutch-speaking regions.
-
D.
Jan Hendrik
Jan Hendrik is the given first name of the renowned Dutch astronomer Jan Oort, a pioneer in the study of the Milky Way and the hypothesized Oort Cloud.
-
E.
Leendert
Leendert is a Dutch masculine given name, notably borne by mathematician Bartel Leendert van der Waerden.
- 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_69d6ab2945d081908a5851c916cbcfb5 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8a73a233081909449ab294d01a512 |
completed | April 10, 2026, 7:31 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f2819229ec81908a3bc5579d661c20 |
completed | April 29, 2026, 10:09 p.m. |
Created at: April 8, 2026, 9:43 p.m.