Triple
T6486254
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wido |
E146517
|
entity |
| Predicate | hasAlternativeSpelling |
P457
|
FINISHED |
| Object | Vido |
E146517
|
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: Vido | Statement: [Wido, hasAlternativeSpelling, Vido]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Vido Context triple: [Wido, hasAlternativeSpelling, Vido]
-
A.
Veere
Veere is a historic harbor town and former trading center located on the island of Walcheren in the Dutch province of Zeeland.
-
B.
Vovin
Vovin is a surname most notably associated with Alexander Vovin, a prominent linguist and specialist in East Asian historical languages.
-
C.
Wido
chosen
Wido is a given name that functions as a variant form of the name Guido, used in various European languages.
-
D.
Vik
Vik is a municipality in Vestland county, Norway, known for its scenic fjord landscapes, historic stave church, and traditional rural communities.
-
E.
Joko
Joko is a romanized variant of the Japanese name Jōkō, which can function as a given name or part of a title.
- 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_69c0090158c08190af0df9a2348d2d52 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c06a706d4c8190b7a3cc8855abcecb |
completed | March 22, 2026, 10:17 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c653b4e91c81908dfa1798a057b21a |
completed | March 27, 2026, 9:53 a.m. |
Created at: March 22, 2026, 4:52 p.m.