Triple
T33890529
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Павел Долгоруков |
E868747
|
entity |
| Predicate | политическая позиция |
P113258
|
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.
politicalPositionDescribed
Indicates that a political role, office, or stance is being characterized or specified in descriptive terms.
-
B.
politicalPositionOnElectoralPolitics
Indicates a stance or viewpoint an entity holds regarding participation in, support for, or opposition to electoral political processes and institutions.
-
C.
politicalAttitude
chosen
Indicates an individual's stance, opinion, or orientation toward political issues, ideologies, or actors.
-
D.
politicalPositionAssociated
Indicates that there is an association between an entity and a specific political position, role, or office.
-
E.
politicallyIn
Indicates that one entity is located within, belongs to, or falls under the political jurisdiction or authority of another entity.
- 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_69f34996761c8190864e42f7c9cf215b |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7051ad6e4819095e82bbd64761803 |
completed | May 3, 2026, 8:19 a.m. |
| PD | Predicate disambiguation | batch_69f700fe24e08190998e2c96fbaaad38 |
completed | May 3, 2026, 8:02 a.m. |
Created at: May 1, 2026, 1:48 a.m.