Triple
T33786795
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | III Государственная дума Российской империи |
E865812
|
entity |
| Predicate | hasSignificantRightFaction |
P134490
|
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: [III Государственная дума Российской империи, hasSignificantRightFaction, правые]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSignificantRightFaction Context triple: [III Государственная дума Российской империи, hasSignificantRightFaction, правые]
-
A.
hasMajorFaction
Indicates that an entity possesses or is associated with a primary or dominant faction within a given context.
-
B.
hasConservativeFaction
chosen
Indicates that an entity includes or is associated with a subgroup characterized by conservative views or positions.
-
C.
hasOpposingFaction
Indicates that one faction stands in opposition or conflict to another faction.
-
D.
hasFaction
Indicates that an entity is affiliated with, belongs to, or is represented by a particular faction or group.
-
E.
foughtForFaction
Indicates that an entity actively participated in or supported a particular faction, typically in a conflict or struggle.
- 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_69f3498ecc2c8190bcd85e3f11dc215e |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fd6f9d600c8190acf495b7fc632e4b |
completed | May 8, 2026, 5:07 a.m. |
| PD | Predicate disambiguation | batch_69fd6e98a2948190a9f78c415ad23b8c |
completed | May 8, 2026, 5:03 a.m. |
Created at: May 1, 2026, 1:45 a.m.