Triple
T1355597
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nicholas |
E28979
|
entity |
| Predicate | hasVariantForm |
P457
|
FINISHED |
| Object | Nikol |
E199508
|
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: Nikol | Statement: [Nicholas, hasVariantForm, Nikol]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Nikol Context triple: [Nicholas, hasVariantForm, Nikol]
-
A.
Nikolay
chosen
Nikolay is a masculine given name of Slavic origin, commonly used in Russian-speaking countries and equivalent to Nicholas in English.
-
B.
Nikolai Nikitin
Nikolai Nikitin was a prominent Soviet structural engineer and architect best known for designing landmark monumental structures, including the towering statue at the Mamayev Kurgan memorial complex and the Ostankino TV Tower in Moscow.
-
C.
Nikitin
Nikitin is a Russian surname borne by numerous notable figures in fields such as art, science, and sports.
-
D.
Niklaus
Niklaus is a masculine given name of Germanic origin, notably borne by Swiss computer scientist Niklaus Wirth.
-
E.
Leonid
Leonid is a masculine given name of Slavic origin, notably borne by Soviet leader Leonid Brezhnev.
- 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_69a498571d248190a0ac9eb02d97097f |
completed | March 1, 2026, 7:49 p.m. |
| NER | Named-entity recognition | batch_69a4c28c8dd0819082f94c9e7c837c5f |
completed | March 1, 2026, 10:49 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ae6515d5f881908f89fa1d6377596e |
completed | March 9, 2026, 6:13 a.m. |
Created at: March 1, 2026, 7:56 p.m.