Triple
T2269604
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gregory |
E50625
|
entity |
| Predicate | hasVariant |
P455
|
FINISHED |
| Object | Grigory |
E315592
|
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: Grigory | Statement: [Gregory, hasVariant, Grigory]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Grigory Context triple: [Gregory, hasVariant, Grigory]
-
A.
Gavril
Gavril is a masculine given name, commonly used in Slavic and Eastern European cultures, that derives from the Hebrew name Gabriel.
-
B.
Vasily
Vasily is a masculine given name of Slavic origin, commonly used in Russian-speaking countries.
-
C.
Grigory Semyonov
Grigory Semyonov was a Russian Cossack military leader and prominent anti-Bolshevik figure who commanded White forces in Siberia and the Russian Far East during the Russian Civil War.
-
D.
Grigori
chosen
Grigori is the given name of Grigori Rasputin, the controversial Russian mystic and advisor to the Romanov royal family in the early 20th century.
-
E.
Oleg
Oleg is a masculine given name of Slavic origin, commonly used in Russia and other Eastern European countries.
- 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_69a88b05910c8190a9a2b1ff230c85f9 |
completed | March 4, 2026, 7:41 p.m. |
| NER | Named-entity recognition | batch_69abc1bd376c8190a43decde599f62e6 |
completed | March 7, 2026, 6:12 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b432e588308190bd331d7b8776e546 |
completed | March 13, 2026, 3:53 p.m. |
Created at: March 4, 2026, 7:48 p.m.