Triple
T30612161
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Василиса |
E779205
|
entity |
| Predicate | существуетВХудожественнойРеальности |
P74686
|
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.
existsWithin
Indicates that one entity is located inside the spatial, temporal, or conceptual boundaries of another entity.
-
B.
appearsInWorkOfArt
chosen
Indicates that an entity is depicted, represented, or otherwise featured within a particular work of art.
-
C.
existedAlong
Indicates that two or more entities were present or in existence during the same time period.
-
D.
realityStatus
Indicates the relationship between an entity and its state of existence or authenticity within a given context or world (e.g., real, fictional, hypothetical, simulated).
-
E.
existsFor
Indicates that something is present, available, or holds true for a particular entity, context, or condition.
- 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_69f689e82bec8190acee385bf0de5345 |
completed | May 2, 2026, 11:34 p.m. |
| PD | Predicate disambiguation | batch_69f67e448a9c8190b591374d98799fe3 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 29, 2026, 8:26 p.m.