Triple
T3585403
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dmitry Donskoy |
E75896
|
entity |
| Predicate | nobleFamily |
P914
|
FINISHED |
| Object | Daniilovichi |
E188958
|
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: Daniilovichi | Statement: [Dmitry Donskoy, nobleFamily, Daniilovichi]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Daniilovichi Context triple: [Dmitry Donskoy, nobleFamily, Daniilovichi]
-
A.
Danilovich
chosen
Danilovich is a Russian patronymic indicating "son of Danilo," commonly used as a middle name in Slavic naming traditions.
-
B.
Romanovich
Romanovich is a Slavic patronymic surname indicating descent from a man named Roman, historically associated with Eastern European nobility such as the rulers of Galicia.
-
C.
Vasilevsky
Vasilevsky is a Russian surname most prominently associated with Aleksandr Vasilevsky, a leading Soviet military commander and Marshal of the Soviet Union during World War II.
-
D.
Lukyanov
Lukyanov is a Russian surname borne by various notable figures in politics, science, and the arts.
-
E.
Semyon
Semyon is a masculine given name of Russian origin, commonly used in Slavic countries.
- 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_69ad85d6dc3c8190b491b79b83e25461 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc135ee3481908ef8dc41af632710 |
completed | March 8, 2026, 6:34 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b43303f1088190be5e4460f579efb8 |
completed | March 13, 2026, 3:53 p.m. |
Created at: March 8, 2026, 3:22 p.m.