Triple
T1405273
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Solidarity |
E31676
|
entity |
| Predicate | opposedSystem |
P17029
|
FINISHED |
| Object | one-party communist rule |
—
|
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 communist rule | Statement: [Solidarity, opposedSystem, one-party communist rule]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: opposedSystem Context triple: [Solidarity, opposedSystem, one-party communist rule]
-
A.
opposedBy
Indicates that one entity actively resists, disagrees with, or works against the actions, views, or position of another entity.
-
B.
opposingForce
Indicates a relationship where one entity actively resists, counters, or works against the actions, goals, or influence of another entity.
-
C.
opposedConference
Indicates that one entity actively resists, counters, or works against another entity within the context of a conference or formal gathering.
-
D.
opposedQualityTo
Indicates that one quality stands in direct opposition or contrast to another quality.
-
E.
opposedFormOfGovernment
chosen
Indicates that one entity holds a stance against, or is in opposition to, the form of government represented by the other entity.
- 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_69a49918e1f88190ba610f9dc8114578 |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c3bc55a08190a4dfe13a5378aff3 |
completed | March 1, 2026, 10:54 p.m. |
| PD | Predicate disambiguation | batch_69a4bf030a388190bc82d30b9233e873 |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:59 p.m.