Triple
T22688644
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sobukwe Clause |
E560987
|
entity |
| Predicate | violatedRight |
P29586
|
FINISHED |
| Object | right to a fair trial |
—
|
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: right to a fair trial | Statement: [Sobukwe Clause, violatedRight, right to a fair trial]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: violatedRight Context triple: [Sobukwe Clause, violatedRight, right to a fair trial]
-
A.
violationOf
chosen
Indicates that one entity breaches, disobeys, or infringes upon a rule, law, agreement, or right associated with another entity.
-
B.
rightsImplicated
Indicates that certain rights are affected, challenged, or brought into question as a consequence of the related action or relationship.
-
C.
violatedPrinciple
Indicates that an entity has broken, disregarded, or acted contrary to a specified rule, norm, or guiding principle.
-
D.
violationExperienced
Indicates that an entity has been subjected to or has undergone a violation, such as a breach of rights, rules, or agreed standards.
-
E.
claimedRight
Indicates that an entity asserts or demands a right or entitlement in relation to another entity or resource.
- 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_69e2454d71b48190a1f80af9f82b6fcf |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f1789931148190925ce9038c16413b |
completed | April 29, 2026, 3:18 a.m. |
| PD | Predicate disambiguation | batch_69ee62b2259c819091ed1387a748b9f3 |
completed | April 26, 2026, 7:08 p.m. |
Created at: April 17, 2026, 3:13 p.m.