Triple
T2878256
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vladimirovich |
E56930
|
entity |
| Predicate | patronymicSuffix |
P42523
|
FINISHED |
| Object | -ovich |
—
|
LITERAL 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: -ovich | Statement: [Vladimirovich, patronymicSuffix, -ovich]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: patronymicSuffix Context triple: [Vladimirovich, patronymicSuffix, -ovich]
-
A.
patronymicName
Indicates that one entity’s name is derived from or based on the given name of a parent or ancestor, typically the father.
-
B.
isMatronymicOf
Indicates that one entity is a name or designation derived from the mother of another entity, typically used as that entity’s family or identifying name.
-
C.
honorificSuffix
Indicates that one entity is a respectful or formal suffix appended to another entity’s name or title.
-
D.
surnameVariant
Indicates that one surname is an alternative spelling, form, or variation of another surname.
-
E.
familyName
Indicates that one entity is the family (last) name associated with another entity (typically a person).
- F. None of above. chosen
Provenance (4 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_69ab4a4ced288190ab6d3e062d10f7f6 |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abe008925c81909683d0ebc6227e5e |
completed | March 7, 2026, 8:21 a.m. |
| PD | Predicate disambiguation | batch_69abdd15cbf08190bf7fea5ea516848a |
completed | March 7, 2026, 8:08 a.m. |
| PDg | Predicate description generation | batch_69abdd96670c8190b727f9ac27dadf67 |
completed | March 7, 2026, 8:11 a.m. |
Created at: March 6, 2026, 10:03 p.m.