Triple
T23533486
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Protection from Harassment Court |
E576631
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | specialised court |
C767
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: specialised court Context triple: [Protection from Harassment Court, instanceOf, specialised court]
-
A.
special court
chosen
A special court is a judicial body established to handle specific types of cases or issues outside the jurisdiction or procedures of ordinary courts, often with specialized rules, judges, or limited subject matter.
-
B.
specialized court registry
A specialized court registry is an administrative office within a particular type of court (e.g., family, commercial, or tax court) responsible for managing case filings, records, scheduling, and procedural documentation specific to that court’s jurisdiction.
-
C.
regional court
A regional court is a judicial body with authority to hear and decide legal cases within a specific geographic area below the national level.
-
D.
specialized arbitration body
A specialized arbitration body is an independent, expert tribunal established to resolve disputes within a particular field or industry through binding or non-binding arbitral decisions.
-
E.
subdivision of court
A subdivision of court is a distinct organizational unit within a larger judicial system, defined by specific jurisdictional scope, case types, or geographic boundaries.
- F. None of above.
Provenance (1 batch)
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_69e245f5a8848190a2ba42e271c6c31f |
completed | April 17, 2026, 2:38 p.m. |
Created at: April 17, 2026, 6:10 p.m.