Triple
T4717765
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hendrik |
E104689
|
entity |
| Predicate | hasVariant |
P455
|
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: [Hendrik, hasVariant, Hendrikus]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Hendrikus Context triple: [Hendrik, hasVariant, 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.
Lodewijk
Lodewijk is the Dutch given name equivalent to Ludwig, historically borne by several notable figures including Dutch nobles and artists.
-
E.
Dirck
Dirck is a Dutch masculine given name historically borne by several notable figures, including artists of the Dutch Golden Age.
- 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_69bd43ec4a348190bc41afae43375e71 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd64261af08190b0d5d86b0e7bacc0 |
completed | March 20, 2026, 3:13 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69be39f7316c8190a6ecd65b707d3fbe |
completed | March 21, 2026, 6:25 a.m. |
Created at: March 20, 2026, 1:18 p.m.