Triple
T24339466
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Надежда |
E613472
|
entity |
| Predicate | связаноСИменем |
P24023
|
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.
associatedName
chosen
Indicates that one entity has an alternative or related name that is linked or connected to another entity.
-
C.
associatedSurname
Indicates that one entity has a surname that is linked or connected to another entity, such as a person, family, or name record.
-
D.
symbolLinked
Indicates a relationship where one symbol is connected or associated with another symbol, typically to show reference, correspondence, or linkage between them.
-
E.
associatedNewName
Indicates that an entity is linked to or identified by a newly assigned name or label.
- 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_69e2d7dcc5a08190b53691130d56cbc4 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f2932324e8819082344cf42eddc274 |
completed | April 29, 2026, 11:24 p.m. |
| PD | Predicate disambiguation | batch_69f287ad30048190b3ad3613486f277f |
completed | April 29, 2026, 10:35 p.m. |
Created at: April 18, 2026, 1:57 a.m.