Triple
T17998599
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lord Justice Clerk |
E430564
|
entity |
| Predicate | legalTitleType |
P11473
|
FINISHED |
| Object | life appointment |
—
|
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: life appointment | Statement: [Lord Justice Clerk, legalTitleType, life appointment]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: legalTitleType Context triple: [Lord Justice Clerk, legalTitleType, life appointment]
-
A.
natureOfTitle
Indicates the specific type or character of a title in relation to the entity it is associated with.
-
B.
hasTitleInLaw
chosen
Indicates that an entity holds or is designated by a specific formal title as defined or recognized in law.
-
C.
titleType
Indicates the specific category or kind of title associated with an entity (e.g., whether it is a main title, alternative title, working title, etc.).
-
D.
legalCodeType
Indicates the specific category or classification of a legal code that applies to an entity or situation.
-
E.
workTitleType
Indicates the specific category or type of a work’s title (e.g., main title, alternative title, translated title) in relation to that work.
- 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_69d8b90364248190a37381adea932f42 |
completed | April 10, 2026, 8:46 a.m. |
| NER | Named-entity recognition | batch_69e4b3e6a2a881908af2d0a4a5053916 |
completed | April 19, 2026, 10:52 a.m. |
| PD | Predicate disambiguation | batch_69e3f90039e4819080527f860dca042e |
completed | April 18, 2026, 9:34 p.m. |
Created at: April 10, 2026, 10:23 a.m.