Triple
T30849273
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Правительство СССР |
E785732
|
entity |
| Predicate | powerBranch |
P95073
|
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: [Правительство СССР, powerBranch, исполнительная власть]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: powerBranch Context triple: [Правительство СССР, powerBranch, исполнительная власть]
-
A.
possibleBranch
Indicates that one entity can serve as an alternative or potential continuation path branching from another entity.
-
B.
powerDistribution
Indicates how authority, control, or influence is allocated and shared among entities within a system or relationship.
-
C.
powerDependsOn
Indicates that the power or effectiveness of one entity is contingent upon, or influenced by, another entity.
-
D.
powerBroker
Indicates a relationship where one entity uses its influence or control to arrange, negotiate, or determine outcomes on behalf of or between other entities.
-
E.
uniformBranch
chosen
Indicates that multiple entities share the same branch, division, or organizational unit within a larger structure.
- 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_69f224b850848190a4af4ccf8ddadcdf |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f74062b9388190b30546cf700a825c |
completed | May 3, 2026, 12:32 p.m. |
| PD | Predicate disambiguation | batch_69f73c802b848190b61a416b7488bd96 |
completed | May 3, 2026, 12:16 p.m. |
Created at: April 29, 2026, 8:46 p.m.