Triple
T2548486
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ministerial Code of the United Kingdom |
E57961
|
entity |
| Predicate | sanction |
P39509
|
FINISHED |
| Object | resignation of a minister |
—
|
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: resignation of a minister | Statement: [Ministerial Code of the United Kingdom, sanction, resignation of a minister]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sanction Context triple: [Ministerial Code of the United Kingdom, sanction, resignation of a minister]
-
A.
typeOfSanction
Indicates the specific category or kind of sanction that is applied in a given situation.
-
B.
enforcement
Indicates the act of compelling compliance with rules, laws, or agreements through monitoring, pressure, or sanctions.
-
C.
canImposeSanctions
Indicates that one entity has the authority or power to apply punitive or restrictive measures (sanctions) against another entity.
-
D.
receivedSanctionFrom
Indicates that one entity has been subjected to a formal penalty, restriction, or disciplinary measure imposed by another entity.
-
E.
sacrifice
Indicates giving up something of value, often for the benefit, protection, or advantage of another entity or goal.
- F. None of above. chosen
Provenance (4 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_69ab4a5212d88190b989ce129f2ad87f |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abd2e7cd4c8190a52cbbf1229441a6 |
completed | March 7, 2026, 7:25 a.m. |
| PD | Predicate disambiguation | batch_69abd0c63964819092d5f578195ae8dd |
completed | March 7, 2026, 7:16 a.m. |
| PDg | Predicate description generation | batch_69abd1c7b6e48190be9a0c31069df797 |
completed | March 7, 2026, 7:20 a.m. |
Created at: March 6, 2026, 9:47 p.m.