Triple
T17116671
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alexey Grigoryevich Dolgorukov |
E415356
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Alexey |
E60595
|
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: Alexey | Statement: [Alexey Grigoryevich Dolgorukov, givenName, Alexey]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Alexey Context triple: [Alexey Grigoryevich Dolgorukov, givenName, Alexey]
-
A.
Alexey
chosen
Alexey is a masculine given name of Slavic origin, commonly used in Russian-speaking countries and derived from the Greek name Alexios, meaning "defender" or "helper."
-
B.
Sergei
Sergei is a masculine given name of Slavic origin, commonly used in Russia and other Eastern European countries.
-
C.
Alexei Aigui
Alexei Aigui is a Russian composer and violinist known for his innovative film scores and contemporary classical music.
-
D.
Anatoly
Anatoly is a masculine given name of Slavic origin, commonly used in Russian-speaking countries.
-
E.
Mikhail
Mikhail is a common Russian male given name, famously borne by Soviet leader Mikhail Gorbachev.
- 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_69d886d090cc8190a39cb94992586905 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3e80660048190832d8f91415dd7d7 |
completed | April 18, 2026, 8:22 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a0180c3be308190ab9972e79287218b |
completed | May 11, 2026, 7:09 a.m. |
Created at: April 10, 2026, 5:35 a.m.