Triple
T8590933
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kosovo judiciary |
E203424
|
entity |
| Predicate | ensuresRight |
P13930
|
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: [Kosovo judiciary, ensuresRight, right to a fair trial]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ensuresRight Context triple: [Kosovo judiciary, ensuresRight, right to a fair trial]
-
A.
ensures
Indicates that one entity guarantees or makes certain that a particular condition, outcome, or state holds for another entity or situation.
-
B.
protectsRight
chosen
Indicates that one entity safeguards, upholds, or defends the legal or moral rights of another entity.
-
C.
establishesRight
Indicates that one entity creates or confers a legal or formal entitlement or privilege upon another entity.
-
D.
heldRight
Indicates that one entity is being held on the right side of another entity.
-
E.
impliedRight
Indicates that one party holds a right or entitlement that is not explicitly stated but is inferred from context, agreements, or established norms.
- 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_69ca832a7f108190b4e4f5648abf4aa2 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cc46c5e8888190b721e791c449b0df |
completed | March 31, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69cc454504448190aaad2af8b17357cd |
completed | March 31, 2026, 10:05 p.m. |
Created at: March 30, 2026, 6:23 p.m.