Triple
T13815261
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vilhelm |
E331997
|
entity |
| Predicate | relatedName |
P3889
|
FINISHED |
| Object | Vilhelms |
E331997
|
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: Vilhelms | Statement: [Vilhelm, relatedName, Vilhelms]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Vilhelms Context triple: [Vilhelm, relatedName, Vilhelms]
-
A.
Vilhelm
chosen
Vilhelm is a masculine given name of Germanic origin, related to William and common in various Scandinavian and European countries.
-
B.
Waldemar
Waldemar is a masculine given name of Germanic origin, historically associated with Scandinavian and Central European nobility and notable figures.
-
C.
Ludvig
Ludvig is a given name, primarily used in Scandinavian countries, that is a variant spelling of Ludwig.
-
D.
Gustav
Gustav is a masculine given name of German origin, borne by several notable historical figures including scientists, artists, and royalty.
-
E.
Miklas
Miklas is an Austrian surname most notably borne by Wilhelm Miklas, who served as President of Austria from 1928 to 1938.
- 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_69d81c59f8808190a851bc56afdc55e9 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de02806e148190996f58934e66d7d8 |
completed | April 14, 2026, 9:01 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f7b8e0112481909deb31f8614f8b93 |
completed | May 3, 2026, 9:06 p.m. |
Created at: April 9, 2026, 10:12 p.m.