Triple
T16987010
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vasily Lukich Dolgorukov |
E412093
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Vasily |
E101378
|
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: Vasily | Statement: [Vasily Lukich Dolgorukov, givenName, Vasily]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Vasily Context triple: [Vasily Lukich Dolgorukov, givenName, Vasily]
-
A.
Vasily
chosen
Vasily is a masculine given name of Slavic origin, commonly used in Russian-speaking countries.
-
B.
Gavril
Gavril is a masculine given name, commonly used in Slavic and Eastern European cultures, that derives from the Hebrew name Gabriel.
-
C.
Vsevolod
Vsevolod is a masculine given name of Slavic origin, most notably borne by the influential Russian theatre director Vsevolod Meyerhold.
-
D.
Innokenty
Innokenty is a masculine given name of Slavic origin, most notably borne by the renowned Russian actor Innokenty Smoktunovsky.
-
E.
Pyotr
Pyotr is a Russian masculine given name, equivalent to Peter, commonly borne by notable historical and cultural figures.
- 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_69d886ca8f348190812768ea8d5055ce |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3d27b58908190a643bcbd105b1849 |
completed | April 18, 2026, 6:50 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a01673e1be08190b39c38fd8115a02c |
completed | May 11, 2026, 5:21 a.m. |
Created at: April 10, 2026, 5:32 a.m.