Triple
T5724802
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Frederik Johannes Willem Reitz |
E126238
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Willem |
E6688
|
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: Willem | Statement: [Frederik Johannes Willem Reitz, givenName, Willem]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Willem Context triple: [Frederik Johannes Willem Reitz, givenName, Willem]
-
A.
Willem
chosen
Willem is a given name, primarily used in Dutch-speaking regions, that corresponds to the English name William.
-
B.
Willem Arondeus
Willem Arondeus was a Dutch artist and openly gay resistance fighter during World War II, best known for his role in the 1943 attack on Amsterdam’s population registry to hinder Nazi persecution of Jews.
-
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.
Lodewijk
Lodewijk is the Dutch given name equivalent to Ludwig, historically borne by several notable figures including Dutch nobles and artists.
- 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_69c0082f723881908ce8bb13a0c0f8b7 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c025085f508190adf5d540bc8a5b1c |
completed | March 22, 2026, 5:21 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c097f0978881908f2b6fb4e6d5e4cd |
completed | March 23, 2026, 1:31 a.m. |
Created at: March 22, 2026, 3:47 p.m.