Triple
T31618610
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | СССР |
E806831
|
entity |
| Predicate | рольВМире |
P6675
|
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.
roleInRussia
Indicates that an entity holds or has held an official or notable role, position, or function within the context of Russia.
-
B.
geopoliticalRole
chosen
Indicates the specific political or strategic function, status, or position an entity holds within or among geopolitical units such as states, regions, or international organizations.
-
C.
internationalRole
Indicates a role, function, or position that an entity holds within an international or cross-border context.
-
D.
ethnicRole
Indicates a role, function, or social position that is specifically associated with or defined by an entity’s ethnicity.
-
E.
loreRole
Indicates the specific narrative or canonical function an entity fulfills within a fictional or mythological lore.
- 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.