Triple
T14920371
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Viks |
E371493
|
entity |
| Predicate | hasSpellingVariant |
P457
|
FINISHED |
| Object | Vikes |
E215976
|
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: Vikes | Statement: [Viks, hasSpellingVariant, Vikes]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Vikes Context triple: [Viks, hasSpellingVariant, Vikes]
-
A.
Vikes
chosen
Vikes is a common shortened nickname for the Minnesota Vikings, the professional American football team based in Minneapolis.
-
B.
Vikes
Vikes is the nickname and athletic brand for the University of Victoria’s varsity sports teams in Canada.
-
C.
Viking
"Viking" is a Russian historical epic film depicting the rise of Prince Vladimir and the Christianization of Kievan Rus.
-
D.
Viking
Viking is a prominent American publishing imprint known for releasing influential fiction and nonfiction titles, including many literary classics and bestsellers.
-
E.
Viking
Viking is a tire brand owned by Continental AG, known for producing reliable and affordable tires for passenger cars and light commercial vehicles.
- 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_69d85cc7ea3481908228b5acb7d06f12 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded62f76bc81909ebc8899096cd1a0 |
completed | April 15, 2026, 12:05 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fe968bbbac8190a258c42b226f9def |
completed | May 9, 2026, 2:06 a.m. |
Created at: April 10, 2026, 2:33 a.m.