Triple
T30199384
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baron Jeffreys of Wem |
E767729
|
entity |
| Predicate | titleNumberOfSecondHolder |
P195277
|
FINISHED |
| Object | 2nd Baron Jeffreys |
—
|
NE NERFINISHED |
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: 2nd Baron Jeffreys | Statement: [Baron Jeffreys of Wem, titleNumberOfSecondHolder, 2nd Baron Jeffreys]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: titleNumberOfSecondHolder Context triple: [Baron Jeffreys of Wem, titleNumberOfSecondHolder, 2nd Baron Jeffreys]
-
A.
titleNumberOfFirstHolder
Indicates the ordinal number assigned to the first person who held a particular title.
-
B.
titleHolderUnder
Indicates that one entity holds a title, position, or rank under the authority, jurisdiction, or hierarchy of another entity.
-
C.
titleHolderIs
Indicates that one entity currently holds or possesses a specific title associated with another entity.
-
D.
titleHolderName
Indicates the name of the person or entity that holds a particular title or position.
-
E.
titleHolderDuring
Indicates that one entity holds a specific title or position during a defined time period in relation to another entity.
- 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_69f2247db1108190835c0727c97637c3 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fdb45537288190b6791078d4a6899f |
completed | May 8, 2026, 10 a.m. |
| PD | Predicate disambiguation | batch_69fdb39ad96481908376d7def9fafc13 |
completed | May 8, 2026, 9:57 a.m. |
| PDg | Predicate description generation | batch_69fdb4544b548190b8971f8055d48caa |
completed | May 8, 2026, 10 a.m. |
Created at: April 29, 2026, 7:30 p.m.