Triple
T4720291
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Orgburo of the CPSU |
E104746
|
entity |
| Predicate | existedInSystem |
P35873
|
FINISHED |
| Object | one-party state |
—
|
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: one-party state | Statement: [Orgburo of the CPSU, existedInSystem, one-party state]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: existedInSystem Context triple: [Orgburo of the CPSU, existedInSystem, one-party state]
-
A.
existedAs
chosen
Indicates that one entity had the status, form, or identity of another entity during a certain time or context.
-
B.
existedUnder
Indicates that one entity existed within the authority, jurisdiction, or domain of another entity during a certain period.
-
C.
establishedSystem
Indicates that an entity has created, set up, or formally put into operation a particular system or structured arrangement.
-
D.
introducedInSystem
Indicates that an entity was first added, implemented, or made available within a particular system.
-
E.
existedAfter
Indicates that one entity came into existence only after another entity already existed.
- 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_69bd43ec4a348190bc41afae43375e71 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd680beb508190b3d74e20e1c64405 |
completed | March 20, 2026, 3:30 p.m. |
| PD | Predicate disambiguation | batch_69bd621ddcd88190903288566f5e5dab |
completed | March 20, 2026, 3:05 p.m. |
Created at: March 20, 2026, 1:18 p.m.