Triple
T16602999
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Berend |
E403376
|
entity |
| Predicate | hasVariant |
P455
|
FINISHED |
| Object | Berend (Dutch form) |
E403376
|
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: Berend (Dutch form) | Statement: [Berend, hasVariant, Berend (Dutch form)]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Berend (Dutch form) Context triple: [Berend, hasVariant, Berend (Dutch form)]
-
A.
Dender (Dutch)
Dender (Dutch) is the Dutch name for the Dender River, a tributary of the Scheldt flowing through Belgium.
-
B.
Berendries
Berendries is a renowned, steep cobbled climb in the Flemish Ardennes of Belgium, frequently featured in professional cycling races such as the Tour of Flanders.
-
C.
Nederboelare
Nederboelare is a village and sub-municipality of the city of Geraardsbergen in the Flemish region of Belgium.
-
D.
Berend
chosen
Berend is a masculine given name of Germanic origin, commonly found in Dutch and German-speaking regions.
-
E.
Niederlauer
Niederlauer is a small municipality in northern Bavaria, Germany, situated in the Franconian Saale valley and known for its rural character within the Rhön region.
- 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_69d883880d0c81908b5fcd454e767b60 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e35d77d97c8190a63330897e49a9c9 |
completed | April 18, 2026, 10:31 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a0075a67abc8190b0f29a9e4589befb |
completed | May 10, 2026, 12:10 p.m. |
Created at: April 10, 2026, 5:17 a.m.