Triple
T5162474
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ramzan Kadyrov |
E116466
|
entity |
| Predicate | sanctionReason |
P42046
|
FINISHED |
| Object | human rights violations |
—
|
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: human rights violations | Statement: [Ramzan Kadyrov, sanctionReason, human rights violations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sanctionReason Context triple: [Ramzan Kadyrov, sanctionReason, human rights violations]
-
A.
reasonForSanctions
chosen
Indicates the underlying cause or justification for imposing sanctions on an entity.
-
B.
sanction
Indicates the imposition of an official penalty or restrictive measure by an authority in response to certain actions or behaviors.
-
C.
isSanctionedBy
Indicates that an entity is subject to official penalties, restrictions, or punitive measures imposed by another authority or organization.
-
D.
typeOfSanction
Indicates the specific category or kind of sanction that is applied in a given situation.
-
E.
sanctioningLevel
Indicates the degree or severity of formal penalties, restrictions, or disciplinary measures imposed in response to a violation or noncompliant behavior.
- 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_69bd445edb3881909b93b34d260717fc |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd79268ea48190a22d3350babc153c |
completed | March 20, 2026, 4:43 p.m. |
| PD | Predicate disambiguation | batch_69bd77b36c008190b91011a9fa52b3d2 |
completed | March 20, 2026, 4:37 p.m. |
Created at: March 20, 2026, 1:44 p.m.