Triple
T27931252
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Court of Protection Rules 2007 |
E707985
|
entity |
| Predicate | typeOfCourtRules |
P95839
|
FINISHED |
| Object | specialist court rules |
—
|
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: specialist court rules | Statement: [Court of Protection Rules 2007, typeOfCourtRules, specialist court rules]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfCourtRules Context triple: [Court of Protection Rules 2007, typeOfCourtRules, specialist court rules]
-
A.
hasTypeOfCourt
Indicates that an entity is associated with or classified by a specific type or category of court.
-
B.
canMakeRulesOfCourt
Indicates that an entity has the authority to establish or prescribe rules governing court procedures or operations.
-
C.
courtStyle
Indicates the manner or stylistic approach in which a court conducts its proceedings or presents its decisions.
-
D.
governingJurisdictionForRules
Indicates the legal or regulatory jurisdiction under whose authority a given set of rules or regulations applies.
-
E.
typeOfRules
chosen
Indicates that one entity specifies or categorizes the kind or category of rules that apply to or are associated with another entity.
- 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_69ef96bbf2c48190a9d0e0291457aab6 |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69fe21b0cba48190b56c39e9f1c0eafa |
completed | May 8, 2026, 5:47 p.m. |
| PD | Predicate disambiguation | batch_69fe204576848190aecf204e2adba5dc |
completed | May 8, 2026, 5:41 p.m. |
Created at: April 27, 2026, 7:03 p.m.