Triple
T9165936
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yefimovich |
E219955
|
entity |
| Predicate | suffixType |
P5567
|
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: [Yefimovich, suffixType, -ovich]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: suffixType Context triple: [Yefimovich, suffixType, -ovich]
-
A.
patronymicSuffix
Indicates that one entity is a suffix added to a personal name to denote lineage or descent from another person, typically the father.
-
B.
termType
chosen
Indicates the classification or category of a term within a system, specifying what kind of term it is (e.g., type, role, or function) in relation to others.
-
C.
usedAsSuffixTo
Indicates that one entity functions as a suffix appended to another entity, typically to modify or extend its meaning.
-
D.
symbolType
Indicates the classification or category of a symbol based on its role, form, or function within a given system.
-
E.
etymologySuffix
Indicates that one term functions as a suffix in the etymological formation or derivation of another term.
- F. None of above.
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_69ca83e3633c81908688a9fa2306ba99 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69ccaa3055048190870211449c78fc4e |
completed | April 1, 2026, 5:16 a.m. |
| PD | Predicate disambiguation | batch_69cc6605c6808190a30d92da006206ac |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:22 p.m.