Triple
T26222168
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Investors Compensation Scheme Ltd v West Bromwich Building Society |
E655792
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | United Kingdom Supreme Court precedent |
C41920
|
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: United Kingdom Supreme Court precedent Context triple: [Investors Compensation Scheme Ltd v West Bromwich Building Society, instanceOf, United Kingdom Supreme Court precedent]
-
A.
United Kingdom constitutional law case
A United Kingdom constitutional law case is a judicial decision that interprets and applies the fundamental principles, structures, and limits of governmental power under the UK’s uncodified constitution.
-
B.
legal case in the United Kingdom
chosen
A legal case in the United Kingdom is a formal dispute brought before a court or tribunal in which parties seek a binding decision on matters of law, fact, or both under UK jurisdiction.
-
C.
British court
A British court is a judicial body within the United Kingdom’s legal system that interprets and applies the law to resolve disputes, administer justice, and uphold legal rights and obligations.
-
D.
United Kingdom statutory rules
United Kingdom statutory rules are legally binding regulations made under the authority of Acts of Parliament, detailing how those Acts are to be implemented and applied in practice.
-
E.
Scottish legal case
A Scottish legal case is a formal dispute brought before a Scottish court or tribunal to interpret and apply Scots law to specific facts and determine the rights and obligations of the parties involved.
- 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_69ee5b4a77e08190bfcb5f8ecdc55abd |
completed | April 26, 2026, 6:36 p.m. |
Created at: April 26, 2026, 8:56 p.m.