Triple
T11766376
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Second All-Russian Congress of Soviets |
E279790
|
entity |
| Predicate | BolshevikMajority |
P1697
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Second All-Russian Congress of Soviets, BolshevikMajority, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: BolshevikMajority Context triple: [Second All-Russian Congress of Soviets, BolshevikMajority, yes]
-
A.
MuscoviteLeader
Indicates a leadership relationship in which the subject serves as a leader or ruler of Muscovites or the Muscovite state.
-
B.
SovietObjective
Indicates that the entity represents a goal, target, or strategic aim pursued by the Soviet Union.
-
C.
establishedAsSocialistState
Indicates that an entity formally created or declared another entity to be a socialist state as its system of governance.
-
D.
overthrownWithHelpOf
Indicates that one entity was removed from power or defeated through the assistance, support, or intervention of another specified entity.
-
E.
hasSovietLeaderParticipant
chosen
Indicates that a Soviet leader is a participant in the referenced event, action, or relationship.
- 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_69d6ab01d2688190ad8ed6bda487eaa5 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a8c2e8b08190a31b1e284fca2aee |
completed | April 10, 2026, 7:37 a.m. |
| PD | Predicate disambiguation | batch_69d8a242cd8c819086ed6c5f292dc8cb |
completed | April 10, 2026, 7:09 a.m. |
Created at: April 8, 2026, 9:41 p.m.