Triple
T18607994
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ivanovna |
E454808
|
entity |
| Predicate | morphologicalRole |
P132766
|
FINISHED |
| Object | 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: suffix | Statement: [Ivanovna, morphologicalRole, suffix]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: morphologicalRole Context triple: [Ivanovna, morphologicalRole, suffix]
-
A.
morphologicalClass
Indicates the classification of an entity based on its morphological form or structural pattern.
-
B.
hasNominalMorphology
Indicates that an entity possesses a system of nominal morphology, such as inflectional or derivational markers on nouns.
-
C.
etymologicalRole
Indicates the specific function or contribution an element has within the historical origin and development of a word or term.
-
D.
notationRole
Indicates a role or function that an entity plays specifically within a system of notation or symbolic representation.
-
E.
notableMorphology
Indicates that an entity is characterized by a distinctive or noteworthy physical form, structure, or shape.
- 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_69d8d38bbe7c8190bdec3138e7d413c9 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e54cff3be8819080ab20045bd18a4d |
completed | April 19, 2026, 9:45 p.m. |
| PD | Predicate disambiguation | batch_69e478cf5e888190a0b1074b0c6525df |
completed | April 19, 2026, 6:40 a.m. |
| PDg | Predicate description generation | batch_69e484121cd48190bf583b4c94636a30 |
completed | April 19, 2026, 7:28 a.m. |
Created at: April 10, 2026, 11:45 a.m.