Triple
T13248148
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Judiciary of Jersey |
E315457
|
entity |
| Predicate | juratsRole |
P23470
|
FINISHED |
| Object | find facts in serious criminal cases |
—
|
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: find facts in serious criminal cases | Statement: [Judiciary of Jersey, juratsRole, find facts in serious criminal cases]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: juratsRole Context triple: [Judiciary of Jersey, juratsRole, find facts in serious criminal cases]
-
A.
juryRole
Indicates that an entity serves in the capacity or function of a juror within a judicial or decision-making process.
-
B.
judicialRole
Indicates that one entity holds or performs a specific official function or position within the judicial system in relation to another entity or legal matter.
-
C.
courtRole
chosen
Indicates the specific capacity or position an entity holds within a court proceeding or judicial context.
-
D.
roleInJudges
Indicates that an entity holds or held a specific role, position, or function within a judicial body or among a group of judges.
-
E.
jurorProfession
Indicates that an individual serves in the professional role or capacity of a juror in a legal proceeding.
- 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_69d806b1072881909e46bd212259c5f0 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98d9e7ea881908abc4b3a54896692 |
completed | April 10, 2026, 11:54 p.m. |
| PD | Predicate disambiguation | batch_69d98bcca7d88190a3e68e99ed3a29e6 |
completed | April 10, 2026, 11:46 p.m. |
Created at: April 9, 2026, 9:24 p.m.