Triple
T23300785
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Central London Property Trust Ltd v High Trees House Ltd |
E590296
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | English contract law case |
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: English contract law case Context triple: [Central London Property Trust Ltd v High Trees House Ltd, instanceOf, English contract law case]
-
A.
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.
-
B.
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.
-
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 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.
-
E.
English lawyer
An English lawyer is a legal professional qualified in the law of England and Wales who advises and represents clients in legal matters, either as a solicitor handling client relations and case preparation or as a barrister specializing in courtroom advocacy.
- 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_69e25d1c0ecc8190a355aa229f06d0e0 |
completed | April 17, 2026, 4:17 p.m. |
Created at: April 17, 2026, 5:04 p.m.