Triple
T30199395
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baron Jeffreys of Wem |
E767729
|
entity |
| Predicate | hasHolderNotability |
P156150
|
FINISHED |
| Object | infamous for severity as a judge |
—
|
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: infamous for severity as a judge | Statement: [Baron Jeffreys of Wem, hasHolderNotability, infamous for severity as a judge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHolderNotability Context triple: [Baron Jeffreys of Wem, hasHolderNotability, infamous for severity as a judge]
-
A.
hasTitleHolderNotability
Indicates that the title holder possesses a notable or distinguished level of recognition or significance.
-
B.
hasNotabilityFor
chosen
Indicates that an entity is notable, recognized, or significant specifically in relation to a given subject, context, or domain.
-
C.
notableHolder
Indicates that a person or entity is a distinguished or prominent holder of a particular position, title, or role.
-
D.
hasNotabilityBasis
Indicates that the notability or significance of one entity is based on, or derived from, another entity or factor.
-
E.
hasNotabilityNote
Indicates that there is an associated note or annotation explaining the significance, prominence, or special relevance of the subject.
- 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_69f2247db1108190835c0727c97637c3 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fb2e940d5c8190bceae77daf4ef512 |
completed | May 6, 2026, 12:05 p.m. |
| PD | Predicate disambiguation | batch_69f9fec70bd881909c658a3c5020318b |
completed | May 5, 2026, 2:29 p.m. |
Created at: April 29, 2026, 7:30 p.m.