Triple
T30574218
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Пепел |
E778198
|
entity |
| Predicate | типПерсонажа |
P60013
|
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.
typeOfCharacter
chosen
Indicates that one entity is a specific kind or category of character in relation to another entity.
-
B.
protagonistType
Indicates the role or category that the main character (protagonist) of a story or scenario belongs to.
-
C.
character1
Indicates that the subject is identified as the first or primary character in a narrative or context.
-
D.
portrayedByCharacterType
Indicates that an entity is depicted or represented by a character of a specified type (e.g., hero, villain, sidekick) in a narrative or media work.
-
E.
styleCharacter
Indicates that one entity defines, influences, or characterizes the stylistic qualities or manner of expression of 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_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.