Triple
T10458150
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Партия народной свободы |
E246599
|
entity |
| Predicate | выступалаПротив |
P437
|
FINISHED |
| Object | самодержавия |
—
|
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: самодержавия | Statement: [Партия народной свободы, выступалаПротив, самодержавия]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: выступалаПротив Context triple: [Партия народной свободы, выступалаПротив, самодержавия]
-
A.
opposedBy
chosen
Indicates that one entity actively resists, disagrees with, or works against the actions, views, or position of another entity.
-
B.
emergedInOppositionTo
Indicates that one entity came into existence or gained prominence specifically as a reaction or counter-movement against another entity.
-
C.
opposedOutcome
Indicates that one entity’s outcome is in conflict with, counters, or works against the outcome associated with another entity.
-
D.
turningPointAgainst
Indicates a pivotal moment or event that shifts momentum or advantage against a particular entity or side.
-
E.
opposedOperation
Indicates that one operation is in conflict with, counters, or works against another operation.
- 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_69d381c04fe08190957c26c526a3b05a |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4fe4a56e08190ab56d762d6a91b01 |
completed | April 7, 2026, 12:53 p.m. |
| PD | Predicate disambiguation | batch_69d4fb7d353c8190a73f439a956c7606 |
completed | April 7, 2026, 12:41 p.m. |
Created at: April 6, 2026, 12:18 p.m.