Triple
T16775640
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boris Danilovich of Moscow |
E407713
|
entity |
| Predicate | patronymic |
P7966
|
FINISHED |
| Object | Danilovich |
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: Danilovich | Statement: [Boris Danilovich of Moscow, patronymic, Danilovich]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Danilovich Context triple: [Boris Danilovich of Moscow, patronymic, Danilovich]
-
A.
Danilovich
chosen
Danilovich is a Russian patronymic indicating "son of Danilo," commonly used as a middle name in Slavic naming traditions.
-
B.
Danilovna
Danilovna is a Russian patronymic suffix used for women, indicating "daughter of Danil" or "daughter of Daniel."
-
C.
Danil
Danil is a masculine given name, common in Slavic countries, that is a variant of Daniel and typically means "God is my judge."
-
D.
Semyonov
Semyonov is a common Russian surname borne by numerous notable figures in fields such as literature, science, and military history.
-
E.
Olgovich
Olgovich is a patronymic surname indicating descent from Oleg, used by members of a medieval Rus' princely lineage.
- 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_69d8839270588190886720d9519bbf8f |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3b039a2a88190865e6a42c830c54d |
completed | April 18, 2026, 4:24 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a00aafe1f8081909b9540aca6e7b9b7 |
completed | May 10, 2026, 3:57 p.m. |
Created at: April 10, 2026, 5:22 a.m.