Triple
T2512189
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wilhelm |
E52726
|
entity |
| Predicate | hasVariant |
P455
|
FINISHED |
| Object | Wilhem |
E52726
|
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: Wilhem | Statement: [Wilhelm, hasVariant, Wilhem]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Wilhem Context triple: [Wilhelm, hasVariant, Wilhem]
-
A.
Willem
Willem is a given name, primarily used in Dutch-speaking regions, that corresponds to the English name William.
-
B.
Wilhelm
chosen
Wilhelm is a Germanic given name, equivalent to William, historically borne by numerous European nobles, rulers, and notable figures.
-
C.
Lodewijk
Lodewijk is the Dutch given name equivalent to Ludwig, historically borne by several notable figures including Dutch nobles and artists.
-
D.
Waldemar
Waldemar is a masculine given name of Germanic origin, historically associated with Scandinavian and Central European nobility and notable figures.
-
E.
Hendrik
Hendrik is a masculine given name of Germanic origin, commonly used in Dutch- and German-speaking countries and related to the name Henry.
- 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_69ab4958e76481908a235377dd921c9e |
completed | March 6, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69abd1efb5c48190a9b47b39a388412b |
completed | March 7, 2026, 7:21 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69afa0425944819096e87fadfce94bc2 |
completed | March 10, 2026, 4:38 a.m. |
Created at: March 6, 2026, 9:46 p.m.