Triple
T359084
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Polish United Workers' Party |
E7807
|
entity |
| Predicate | lostMonopolyOfPower |
P8109
|
FINISHED |
| Object | 1989 |
—
|
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: 1989 | Statement: [Polish United Workers' Party, lostMonopolyOfPower, 1989]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lostMonopolyOfPower Context triple: [Polish United Workers' Party, lostMonopolyOfPower, 1989]
-
A.
lostMostPowersTo
Indicates that one entity has been deprived of the majority of its powers, abilities, or authority as a result of another entity’s actions or influence.
-
B.
powerDecline
chosen
Indicates a decrease or weakening in the level, intensity, or effectiveness of power exerted or possessed in a given context.
-
C.
lostPowerIn
Indicates that an entity has experienced a loss of electrical or functional power while in or at a specified location or context.
-
D.
lostPower
Indicates that an entity has ceased to have electrical or functional power it previously possessed.
-
E.
exclusivePower
Indicates that one entity holds sole authority or control over another entity or a specific domain, excluding others from sharing that power.
- 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_69a2e7e880008190a6ad7e06e5d03007 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ebb248608190b060553219616043 |
completed | Feb. 28, 2026, 1:20 p.m. |
| PD | Predicate disambiguation | batch_69a2e95aeed48190b5e48865cc964938 |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.