Triple
T359063
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Polish United Workers' Party |
E7807
|
entity |
| Predicate | heldMonopolyOfPower |
P4392
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Polish United Workers' Party, heldMonopolyOfPower, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: heldMonopolyOfPower Context triple: [Polish United Workers' Party, heldMonopolyOfPower, yes]
-
A.
exercisedPowerOver
Indicates that one entity exerted control, influence, or authority over another entity.
-
B.
exclusivePower
chosen
Indicates that one entity holds sole authority or control over another entity or a specific domain, excluding others from sharing that power.
-
C.
majorPowerIn
Indicates that an entity holds significant political, economic, or military influence within a specified domain, region, or context.
-
D.
occupyingPower
Indicates that one entity holds military or political control over a territory that it does not legally own, typically as an occupying authority.
-
E.
cameToPowerIn
Indicates the time or context in which an entity assumed control, authority, or leadership over a group, organization, or territory.
- 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.