Triple
T7512499
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Russian State (Omsk Government) |
E177553
|
entity |
| Predicate | collapsedDueTo |
P77396
|
FINISHED |
| Object | military defeats by the Red Army |
—
|
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: military defeats by the Red Army | Statement: [Russian State (Omsk Government), collapsedDueTo, military defeats by the Red Army]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: collapsedDueTo Context triple: [Russian State (Omsk Government), collapsedDueTo, military defeats by the Red Army]
-
A.
collapsedAfter
Indicates that one entity collapsed at some point in time after another specified event or entity’s collapse.
-
B.
collapsedDuring
Indicates that one entity structurally failed or fell down while another specified event or process was occurring.
-
C.
collapsedWith
Indicates that one entity fell down or caved in together with another entity, typically as part of the same collapse event.
-
D.
collapsedOn
Indicates that one entity physically fell or caved in onto another entity, ending up resting on or covering it.
-
E.
collapseDate
Indicates the date on which something structurally or functionally failed, broke down, or ceased to exist.
- F. None of above. chosen
Provenance (4 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_69c69f276b108190af2cc790b6554544 |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f5d52b2c8190ba32b1575756fa7c |
completed | March 27, 2026, 9:25 p.m. |
| PD | Predicate disambiguation | batch_69c6f4d44e9481909813e073b194f6f4 |
completed | March 27, 2026, 9:21 p.m. |
| PDg | Predicate description generation | batch_69c6f574d8a8819095749518dad13791 |
completed | March 27, 2026, 9:24 p.m. |
Created at: March 27, 2026, 3:45 p.m.