Triple
T31414207
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Justices of the Peace Act 1997 |
E801346
|
entity |
| Predicate | hasTypeOfMagistrate |
P197327
|
FINISHED |
| Object | lay magistrate |
—
|
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: lay magistrate | Statement: [Justices of the Peace Act 1997, hasTypeOfMagistrate, lay magistrate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypeOfMagistrate Context triple: [Justices of the Peace Act 1997, hasTypeOfMagistrate, lay magistrate]
-
A.
hasMagistrate
Indicates that an entity is under the authority, jurisdiction, or oversight of a specific magistrate.
-
B.
magistrateOf
Indicates that a person holds the official position or role of magistrate in relation to a particular jurisdiction, institution, or group.
-
C.
hasMagistrateJudges
Indicates that one legal jurisdiction, court, or governing body includes or is served by one or more magistrate judges.
-
D.
magistrateJudgeTerm
Indicates that a magistrate judge holds or serves a specific judicial term or period of office.
-
E.
hasMagistratesCourtsFunction
Indicates that an entity performs, holds, or is assigned the official role or responsibilities of a magistrates’ court.
- F. None of above. chosen
Provenance (4 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_69f348c0dd648190bf2fd7642f78eb06 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fe87b609888190913b0c3f787ecdba |
completed | May 9, 2026, 1:02 a.m. |
| PD | Predicate disambiguation | batch_69fe8731af48819092084f6f74bf052d |
completed | May 9, 2026, 1 a.m. |
| PDg | Predicate description generation | batch_69fe87b52bd4819087d6d338fe47c97c |
completed | May 9, 2026, 1:02 a.m. |
Created at: April 30, 2026, 8:41 p.m.