Triple
T24133742
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | АН СССР |
E598024
|
entity |
| Predicate | причинаПрекращения |
P13662
|
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.
end cause
Indicates that one event or action brings about the termination or cessation of another event, state, or process.
-
B.
reasonForDisbandment
chosen
Indicates the cause or circumstance that led to a group, organization, or entity being dissolved or disbanded.
-
C.
reasonForDiscontinuation
Indicates that one entity specifies the cause or justification for stopping, ending, or withdrawing another entity, process, or activity.
-
D.
inactivationReason
Indicates the reason or cause for which an entity, status, or process has been deactivated or made inactive.
-
E.
reasonForAnnulment
Indicates the specific cause or grounds on which a prior decision, agreement, or status is formally annulled or declared invalid.
- 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_69e288c92e448190ac57034fa0c863ce |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1df79bfd08190970ed1b3f14ebc8b |
completed | April 29, 2026, 10:37 a.m. |
| PD | Predicate disambiguation | batch_69f1765650fc8190a6bc1eb512b240bf |
completed | April 29, 2026, 3:09 a.m. |
Created at: April 17, 2026, 11:26 p.m.