Triple
T4560366
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Konstantin Stanislavski |
E120576
|
entity |
| Predicate | patronymicName |
P7966
|
FINISHED |
| Object | Sergeyevich |
E64229
|
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: Sergeyevich | Statement: [Konstantin Stanislavski, patronymicName, Sergeyevich]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Sergeyevich Context triple: [Konstantin Stanislavski, patronymicName, Sergeyevich]
-
A.
Sergei
chosen
Sergei is a masculine given name of Slavic origin, commonly used in Russia and other Eastern European countries.
-
B.
Vasilyevich
Vasilyevich is the Russian patronymic indicating "son of Vasily," famously used in the full name of Ivan IV (Ivan Vasilyevich), the first tsar of Russia.
-
C.
Semyon
Semyon is a masculine given name of Russian origin, commonly used in Slavic countries.
-
D.
Alekseevich
Alekseevich is a Russian patronymic surname or middle name derived from the given name Aleksey, indicating "son of Aleksey."
-
E.
Anatolyevich
Anatolyevich is a Russian patronymic given name indicating that a person is the son of someone named Anatoly.
- 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_69bd4636f1648190a701445c2fcd9c17 |
completed | March 20, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69bd582b871c8190be0b70c76d639000 |
completed | March 20, 2026, 2:22 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69bdc59b2514819091f3845307cb1c8b |
completed | March 20, 2026, 10:09 p.m. |
Created at: March 20, 2026, 1:09 p.m.