Triple
T30612173
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Василиса |
E779205
|
entity |
| Predicate | литературноеНаправлениеПроизведения |
P22130
|
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 relationship where a person or entity is a character appearing in a particular literary or artistic work.
-
B.
literaryGenreOfWorkAppearedIn
Indicates the literary genre of the work in which a given entity (such as a text, character, or element) appears.
-
C.
literaryUnit
Indicates that one entity is a distinct segment or component (such as a chapter, scene, or passage) within a larger literary work or text.
-
D.
literaryGenreOfWork
chosen
Indicates that a work belongs to or is classified under a particular literary genre.
-
E.
literaryCenter
Indicates that a location functions as a primary hub or focal point for literary activity, such as writing, publishing, or literary culture.
- 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_69f224a21fc08190abd9d8dd9eb6bb4c |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f68a16debc8190a12f5f65ced055d7 |
completed | May 2, 2026, 11:34 p.m. |
| PD | Predicate disambiguation | batch_69f6860def1c81909d79e1f088c4b5e5 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 29, 2026, 8:26 p.m.