Triple
T30436210
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Дом Советов РСФСР |
E774317
|
entity |
| Predicate | являетсяСимволом |
P89328
|
FINISHED |
| Object | российской государственности начала 1990-х годов |
—
|
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: российской государственности начала 1990-х годов | Statement: [Дом Советов РСФСР, являетсяСимволом, российской государственности начала 1990-х годов]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: являетсяСимволом Context triple: [Дом Советов РСФСР, являетсяСимволом, российской государственности начала 1990-х годов]
-
A.
symbolizes
Indicates that one entity stands for, represents, or is used as a sign for another entity, concept, or idea.
-
B.
symbolizedIn
chosen
Indicates that one entity serves as a symbol or representation of another entity.
-
C.
symbolIs
Indicates that one entity serves as the symbolic representation or sign of another entity.
-
D.
appearsWithSymbol
Indicates that one entity is shown or presented together with a particular symbol in the same visual or contextual setting.
-
E.
typicalSymbol
Indicates that something serves as a characteristic or commonly recognized symbol representing something else.
- 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_69f22492d2a88190995ce8745d9becaa |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f68694ff888190b85abd31df01a71c |
completed | May 2, 2026, 11:19 p.m. |
| PD | Predicate disambiguation | batch_69f678d2196c8190b9d0d2fcd47cc539 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 29, 2026, 8:07 p.m.