Triple
T31618582
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | СССР |
E806831
|
entity |
| Predicate | правящаяПартия |
P352
|
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.
AngreifendePartei
Indicates a party that initiates or carries out an attack against another party.
-
B.
VerteidigendePartei
Indicates that an entity functions as the defending party in a legal dispute or proceeding.
-
C.
otherMajorParty
Indicates that an entity is affiliated with a major political party other than a specified primary or reference party.
-
D.
religiousParty
Indicates that an entity is a political party whose identity, platform, or activities are primarily based on or strongly influenced by a particular religion or religious principles.
-
E.
politicalParty
chosen
Indicates that an entity is affiliated with, belongs to, or is a member of a specific political party.
- 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_69f348d7883c8190b6c13ab92b7ef076 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6a8acae308190b3450346a6bb55bc |
completed | May 3, 2026, 1:45 a.m. |
| PD | Predicate disambiguation | batch_69f6a75656e081908739ed9e2f600e42 |
completed | May 3, 2026, 1:39 a.m. |
Created at: April 30, 2026, 10:40 p.m.