Triple
T9086537
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mironovich |
E217769
|
entity |
| Predicate | formedBySuffix |
P42400
|
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: [Mironovich, formedBySuffix, -ovich]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formedBySuffix Context triple: [Mironovich, formedBySuffix, -ovich]
-
A.
formedBy
Indicates that something comes into existence or is created as a result of a specific agent, process, or combination of components.
-
B.
usedAsSuffixTo
chosen
Indicates that one entity functions as a suffix appended to another entity, typically to modify or extend its meaning.
-
C.
formedTo
Indicates that one entity was created, established, or organized for the purpose of serving, supporting, or enabling another entity or activity.
-
D.
formedByUnionOf
Indicates that something is created or defined as the union or combination of multiple other things.
-
E.
patronymicSuffix
Indicates that one entity is a suffix added to a personal name to denote lineage or descent from another person, typically the father.
- 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_69ca83d7a0388190ba1af89ed7ba36f9 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cc9654cb3c819089fa8c0ab0841c81 |
completed | April 1, 2026, 3:51 a.m. |
| PD | Predicate disambiguation | batch_69cc65fa79bc81908b46f05c8bba920f |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:13 p.m.