Triple
T30583146
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Internal security courts |
E778435
|
entity |
| Predicate | legalIssuesRaised |
P4511
|
FINISHED |
| Object | compliance with fair trial guarantees |
—
|
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: compliance with fair trial guarantees | Statement: [Internal security courts, legalIssuesRaised, compliance with fair trial guarantees]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: legalIssuesRaised Context triple: [Internal security courts, legalIssuesRaised, compliance with fair trial guarantees]
-
A.
mainLegalIssue
Indicates the primary legal question or dispute that is central to a case or legal matter.
-
B.
hasLegalIssue
chosen
Indicates that an entity is involved in, associated with, or subject to a legal problem, dispute, or proceeding.
-
C.
legalMatters
Indicates that one entity is involved with, concerned about, or responsible for legal issues, processes, or obligations related to another entity or context.
-
D.
legalDisputeSubject
Indicates that a legal dispute concerns, involves, or is specifically about the referenced subject or matter.
-
E.
courtIssue
Indicates that a court formally issues or hands down a legal document, order, ruling, or decision to the relevant parties.
- 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_69f224a04b248190b0ca443ec86207b8 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fe21b0cba48190b56c39e9f1c0eafa |
completed | May 8, 2026, 5:47 p.m. |
| PD | Predicate disambiguation | batch_69fe204576848190aecf204e2adba5dc |
completed | May 8, 2026, 5:41 p.m. |
Created at: April 29, 2026, 8:23 p.m.