Triple
T6701883
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Konstantin Mereschkowski |
E152898
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Konstantin |
E141815
|
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: Konstantin | Statement: [Konstantin Mereschkowski, givenName, Konstantin]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Konstantin Context triple: [Konstantin Mereschkowski, givenName, Konstantin]
-
A.
Konstantin
chosen
Konstantin is a masculine given name of Latin origin, widely used in Slavic and other European cultures, meaning “steadfast” or “constant.”
-
B.
Vsevolod
Vsevolod is a masculine given name of Slavic origin, most notably borne by the influential Russian theatre director Vsevolod Meyerhold.
-
C.
Oleg
Oleg is a masculine given name of Slavic origin, commonly used in Russia and other Eastern European countries.
-
D.
Vasily
Vasily is a masculine given name of Slavic origin, commonly used in Russian-speaking countries.
-
E.
Timofei
Timofei is a masculine given name of Slavic origin, commonly used in Russian-speaking countries and related to the name Timo.
- 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_69c68807adbc8190b8632df42b39eda0 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d0e5eb0c81908c4fa3febd2d23ca |
completed | March 27, 2026, 6:48 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c7616ff6fc8190b4e9e7810be9064b |
completed | March 28, 2026, 5:04 a.m. |
Created at: March 27, 2026, 2:06 p.m.