Triple
T18472889
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alexei Antonovich of Brunswick |
E451346
|
entity |
| Predicate | patronymicName |
P7966
|
FINISHED |
| Object | Antonovich |
—
|
NE NERFINISHED |
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: Antonovich | Statement: [Alexei Antonovich of Brunswick, patronymicName, Antonovich]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Antonovich Context triple: [Alexei Antonovich of Brunswick, patronymicName, Antonovich]
-
A.
Antonovich
chosen
Antonovich is the patronymic of Ivan VI of Russia, indicating he was the son of a man named Anton.
-
B.
Anatoly
Anatoly is a masculine given name of Slavic origin, commonly used in Russian-speaking countries.
-
C.
Anatolyevich
Anatolyevich is a Russian patronymic given name indicating that a person is the son of someone named Anatoly.
-
D.
Antoshka
Antoshka is a common Russian diminutive form of the male given name Anton, often used affectionately or informally.
-
E.
Adamovich
Adamovich is a Slavic surname borne by various notable figures, including Russian poet and literary critic Georgy Adamovich.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8d38465a0819099b9b42d2a662ac1 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e530617e48819091240d4405e53aaa |
completed | April 19, 2026, 7:43 p.m. |
Created at: April 10, 2026, 11:34 a.m.