Triple
T1854768
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | State Committee on the State of Emergency in the USSR |
E41675
|
entity |
| Predicate | membersArrested |
P22280
|
FINISHED |
| Object | 1991-08-22 |
—
|
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: 1991-08-22 | Statement: [State Committee on the State of Emergency in the USSR, membersArrested, 1991-08-22]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: membersArrested Context triple: [State Committee on the State of Emergency in the USSR, membersArrested, 1991-08-22]
-
A.
numberOfArrests
Indicates the count of times an entity has been arrested.
-
B.
arrestedFor
Indicates that an authority has taken someone into custody because they are suspected or accused of committing a specified offense or wrongdoing.
-
C.
arrests
chosen
Indicates that one entity, typically an authority figure, seizes and detains another entity under legal or official power.
-
D.
criminalStatus
Indicates the legal condition of an entity with respect to criminal law, such as whether they are accused, convicted, or cleared of a crime.
-
E.
reArrested
Indicates that an entity is arrested again after having been previously released or arrested before.
- 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_69a8864a83848190a4ec02721306c511 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb231de14819091da3a20ed03c430 |
completed | March 7, 2026, 5:05 a.m. |
| PD | Predicate disambiguation | batch_69abafde4598819099d8229128348fd3 |
completed | March 7, 2026, 4:55 a.m. |
Created at: March 4, 2026, 7:33 p.m.