Triple
T15543132
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Petrenko |
E370531
|
entity |
| Predicate | hasMorphologicalElement |
P106688
|
FINISHED |
| Object | -enko suffix |
—
|
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: -enko suffix | Statement: [Petrenko, hasMorphologicalElement, -enko suffix]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMorphologicalElement Context triple: [Petrenko, hasMorphologicalElement, -enko suffix]
-
A.
hasMorphologicalState
Indicates that an entity possesses or is characterized by a particular morphological condition, form, or structural state.
-
B.
containsMorpheme
chosen
Indicates that one linguistic unit (such as a word or stem) includes a particular morpheme as one of its meaningful subparts.
-
C.
hasLinguisticElement
Indicates that one entity includes, is associated with, or is characterized by a particular linguistic component such as a word, phrase, symbol, or other language element.
-
D.
hasMorphologicalType
Indicates that an entity possesses or is classified by a particular morphological type or structural form.
-
E.
hasVerbalMorphology
Indicates that one linguistic element exhibits verbal inflectional properties or patterns in relation to another.
- 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_69d85cc521a08190921fb50319dddc34 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04432c3808190bb5b653bf8de30c6 |
completed | April 16, 2026, 2:06 a.m. |
| PD | Predicate disambiguation | batch_69deda7a95c48190bbe29fadcf17191a |
completed | April 15, 2026, 12:23 a.m. |
Created at: April 10, 2026, 4:07 a.m.