Triple
T31618612
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | СССР |
E806831
|
entity |
| Predicate | военныйБлок |
P15789
|
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.
militaryIssue
Indicates that one entity formally provides or distributes military-related items, orders, or directives to another entity.
-
B.
militaryConflict
Indicates a relationship where two or more parties are engaged in organized, armed hostilities or warfare against each other.
-
C.
militaryBacked
Indicates that one entity is supported, protected, or sustained by the military power or armed forces of another entity.
-
D.
countryMilitary
Indicates that a country possesses, controls, or is associated with a particular military force or armed organization.
-
E.
militarySystem
chosen
Indicates a relationship where an entity functions as, belongs to, or is characterized by a particular military organizational or operational system.
- 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.