Triple
T18011896
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saint Willehad |
E430904
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Willehad |
—
|
NE NERFINISHED |
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: Willehad | Statement: [Saint Willehad, givenName, Willehad]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Willehad Context triple: [Saint Willehad, givenName, Willehad]
-
A.
Willehad
chosen
Willehad was an 8th-century Anglo-Saxon missionary and the first Bishop of Bremen, known for his key role in converting the Frisian and Saxon peoples to Christianity.
-
B.
Wille
Wille is the given name of Finnish politician Wille Rydman, known for his roles in national politics.
-
C.
Wittekind
Wittekind is an alternative spelling of Widukind, the 8th-century Saxon noble and military leader who resisted Charlemagne’s Frankish conquest and Christianization of Saxony.
-
D.
Willahelm
Willahelm is a Germanic given name that is the historical root of names like Willem and William, traditionally meaning "resolute protector."
-
E.
Walwenus
Walwenus is an alternative name for Walwen, a figure likely associated with medieval or legendary traditions.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8b904530081908bf341d842464856 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4b51fc108819089e6c130a89811bc |
completed | April 19, 2026, 10:57 a.m. |
Created at: April 10, 2026, 10:24 a.m.