Triple
T30574219
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Пепел |
E778198
|
entity |
| Predicate | темаСвязанаС |
P47748
|
FINISHED |
| Object | нравственное перерождение |
—
|
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: нравственное перерождение | Statement: [Пепел, темаСвязанаС, нравственное перерождение]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: темаСвязанаС Context triple: [Пепел, темаСвязанаС, нравственное перерождение]
-
A.
themeFor
Indicates that something serves as the central subject, topic, or focus for another thing (such as an event, work, or activity).
-
B.
theme
Indicates the entity that is the primary participant or content affected or characterized by an action, event, or state.
-
C.
associatedThemeElements
Indicates a relationship where certain elements are linked to, or grouped under, a particular theme as its related components.
-
D.
followsInTheme
Indicates that one element continues or succeeds another while maintaining the same theme or thematic context.
-
E.
sharesThemeWith
chosen
Indicates that two entities are related by having the same or closely similar underlying theme or subject matter.
- 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_69f2249f8c148190ae7eb3912cde112a |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f689167878819093cb4f58efd47e2e |
completed | May 2, 2026, 11:30 p.m. |
| PD | Predicate disambiguation | batch_69f67e42d6688190b60e91d2c388c555 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 29, 2026, 8:22 p.m.