Triple
T30713096
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Viscount Savile |
E781944
|
entity |
| Predicate | higherTitleHeldByHolder |
P100478
|
FINISHED |
| Object | Earl of Sussex |
—
|
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: Earl of Sussex | Statement: [Viscount Savile, higherTitleHeldByHolder, Earl of Sussex]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: higherTitleHeldByHolder Context triple: [Viscount Savile, higherTitleHeldByHolder, Earl of Sussex]
-
A.
higherTitleHeldBySamePerson
chosen
Indicates that the same individual who holds one title also holds another, higher-ranking title.
-
B.
higherTitleSubsequentlyCreatedForHolder
Indicates that a higher-ranking title was created at a later time specifically for the same individual who already held the original title.
-
C.
titleHeldTo
Indicates that one entity holds or possesses a specific title in relation to another entity or context.
-
D.
lastHolderTitle
Indicates the official title or position held by the most recent holder of a given role, asset, or entity.
-
E.
titleHolderIs
Indicates that one entity currently holds or possesses a specific title 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_69f224acd24481908ed5f96f0d69b5dd |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f78fd5a6388190bfda4bbb2e222e5b |
completed | May 3, 2026, 6:11 p.m. |
| PD | Predicate disambiguation | batch_69f78e2ac3fc819081a45c6841375c8d |
completed | May 3, 2026, 6:04 p.m. |
Created at: April 29, 2026, 8:35 p.m.