Triple
T10967020
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Justice of the Peace for Lancashire |
E259127
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | judicial office in England |
C940
|
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: judicial office in England Context triple: [Justice of the Peace for Lancashire, instanceOf, judicial office in England]
-
A.
judicial office
chosen
A judicial office is an official position within the judiciary in which an individual is authorized to interpret and apply the law, preside over legal proceedings, and issue binding decisions.
-
B.
public office in England and Wales
A public office in England and Wales is a position conferred by the state or a public authority that carries ongoing duties to the public, is created or recognized by law, and involves the exercise of public functions or powers.
-
C.
Justiciar of England
The Justiciar of England was the king’s chief minister and principal royal administrator in medieval England, acting as regent in the monarch’s absence and overseeing justice, finance, and governance.
-
D.
Commonwealth of England office
A Commonwealth of England office is an administrative or governmental position or institution that operated under the republican regime of England (1649–1660), responsible for executing the functions of state in the absence of a monarchy.
-
E.
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.
- 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_69d6aa88500c819097d7032ca578e74f |
completed | April 8, 2026, 7:20 p.m. |
Created at: April 8, 2026, 9:24 p.m.