Triple
T16816167
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Matvei Bronstein |
E408754
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Matvei |
E787763
|
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: Matvei | Statement: [Matvei Bronstein, givenName, Matvei]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Matvei Context triple: [Matvei Bronstein, givenName, Matvei]
-
A.
Matvey
chosen
Matvey is a masculine given name of Slavic origin, commonly used in Russian-speaking countries and equivalent to the name Matthew.
-
B.
Yakov
Yakov was the eldest son of Soviet leader Joseph Stalin, known for his troubled relationship with his father and his death as a prisoner of war during World War II.
-
C.
Semyon
Semyon is a masculine given name of Russian origin, commonly used in Slavic countries.
-
D.
Yefim
Yefim is a masculine given name of Hebrew origin, commonly used in Russian-speaking countries.
-
E.
Yefimovich
Yefimovich is the Russian patronymic derived from the male given name Yefim, famously borne by Grigori Rasputin as part of his full name.
- 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_69d88394566c8190b3dcbdc72935f7fa |
completed | April 10, 2026, 4:59 a.m. |
| NER | Named-entity recognition | batch_69e3b2e1de908190aa3508770fb865cf |
completed | April 18, 2026, 4:35 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a00bb0f863081908e74dc4a7c91e91d |
completed | May 10, 2026, 5:06 p.m. |
Created at: April 10, 2026, 5:23 a.m.