Triple
T4366225
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Katerina Mikhailovna Maslova |
E98778
|
entity |
| Predicate | keyThemeAssociated |
P25955
|
FINISHED |
| Object | moral struggle |
—
|
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: moral struggle | Statement: [Katerina Mikhailovna Maslova, keyThemeAssociated, moral struggle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: keyThemeAssociated Context triple: [Katerina Mikhailovna Maslova, keyThemeAssociated, moral struggle]
-
A.
primaryThemeAssociation
Indicates that one entity is the main or central theme associated with another entity.
-
B.
majorThemeAssociation
Indicates that one entity is associated with another as a primary or central theme.
-
C.
themeFor
chosen
Indicates that something serves as the central subject, topic, or focus for another thing (such as an event, work, or activity).
-
D.
sharesThemeWith
Indicates that two entities are related by having the same or closely similar underlying theme or subject matter.
-
E.
key
Indicates that one entity functions as a key (literal or metaphorical) that unlocks, enables access to, or provides a crucial solution or control over another entity.
- 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_69b3454c772081908e20173e379e8ebe |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b35200263081909bb326a4d7a8db99 |
completed | March 12, 2026, 11:53 p.m. |
| PD | Predicate disambiguation | batch_69b34f53e3cc8190bf5d4dbe2413bf65 |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:17 p.m.