Triple
T30574240
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Пепел |
E778198
|
entity |
| Predicate | связанСМотивом |
P33019
|
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.
повʼязанеЗ
Indicates a general association or connection between one entity and another.
-
B.
inspiredByOrRelatedTo
Indicates that one entity draws inspiration from, is influenced by, or is otherwise thematically or conceptually connected to another entity.
-
C.
sharesMotifsWith
chosen
Indicates that two entities contain or employ similar recurring themes, patterns, or symbolic elements.
-
D.
relatedToMotto
Indicates that one entity has an association or connection with a motto, such as embodying, expressing, or being defined by that motto.
-
E.
moreCloselyRelatedTo
Indicates that one entity has a stronger or closer relationship, connection, or similarity to a second entity than to some other reference 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_69f2249f8c148190ae7eb3912cde112a |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6953bafb88190a860e9c68a3dd4b2 |
completed | May 3, 2026, 12:22 a.m. |
| PD | Predicate disambiguation | batch_69f690ed5d008190831cf8e44cce28af |
completed | May 3, 2026, 12:03 a.m. |
Created at: April 29, 2026, 8:22 p.m.