Triple
T14444362
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Magisterial District Judge |
E358164
|
entity |
| Predicate | mustBeLawyer |
P48883
|
FINISHED |
| Object | not always required by statute |
—
|
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: not always required by statute | Statement: [Magisterial District Judge, mustBeLawyer, not always required by statute]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mustBeLawyer Context triple: [Magisterial District Judge, mustBeLawyer, not always required by statute]
-
A.
legalProfessionIncludes
Indicates that a legal profession or role encompasses, involves, or includes another specified legal function, specialization, or activity.
-
B.
numberOfLawyers
Indicates the quantity of lawyers associated with a given entity or situation.
-
C.
allowsRepresentationByLawyers
Indicates that one party permits or recognizes the right of another party to be represented by lawyers in a given context or proceeding.
-
D.
judgesMustBeLawyers
chosen
Indicates that anyone serving as a judge is required to be a lawyer.
-
E.
haveLaw
Indicates that a governing body or jurisdiction possesses, enforces, or is characterized by a particular law or set of laws.
- F. None of above.
Provenance (3 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_69d82794dfa081909b9134ad2e32244b |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de915e76f481909fe9462f964b5b1c |
completed | April 14, 2026, 7:11 p.m. |
| PD | Predicate disambiguation | batch_69de5c3a02fc819097373f97a260cdeb |
completed | April 14, 2026, 3:24 p.m. |
Created at: April 10, 2026, 1:19 a.m.