Triple
T1080846
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | High Court of Justiciary |
E23940
|
entity |
| Predicate | governsAreaOfLaw |
P2167
|
FINISHED |
| Object | criminal law |
—
|
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: criminal law | Statement: [High Court of Justiciary, governsAreaOfLaw, criminal law]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: governsAreaOfLaw Context triple: [High Court of Justiciary, governsAreaOfLaw, criminal law]
-
A.
branchOfLaw
Indicates a relationship where one legal field or discipline is a subdivision or specialized area within a broader body of law.
-
B.
legalJurisdiction
Indicates the legal authority or geographic area whose laws and courts have the power to govern, regulate, or adjudicate matters involving the related entities.
-
C.
legalArea
chosen
Indicates the specific field or branch of law that a legal matter, case, or document pertains to.
-
D.
typeOfLaw
Indicates that one entity is a specific category or kind of law to which the other entity pertains.
-
E.
governmentJurisdiction
Indicates the governmental body or authority that has legal power, control, or regulatory oversight over a given entity or activity.
- 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_69a493f1ddf48190a99d54b00e99f8ce |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b946af788190b400644a2dec68c3 |
completed | March 1, 2026, 10:10 p.m. |
| PD | Predicate disambiguation | batch_69a4b73d9f08819093668104f129840e |
completed | March 1, 2026, 10:01 p.m. |
Created at: March 1, 2026, 7:42 p.m.