Triple
T32928899
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baron Eldon |
E842345
|
entity |
| Predicate | hasHigherTitleHeldByFirstHolder |
P100478
|
FINISHED |
| Object | Earl of Eldon |
—
|
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 Eldon | Statement: [Baron Eldon, hasHigherTitleHeldByFirstHolder, Earl of Eldon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHigherTitleHeldByFirstHolder Context triple: [Baron Eldon, hasHigherTitleHeldByFirstHolder, Earl of Eldon]
-
A.
alsoHeldByFirstHolder
Indicates that something possessed or held by a second holder is (or was) also possessed or held by the first holder.
-
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.
higherTitleHeldBySamePerson
chosen
Indicates that the same individual who holds one title also holds another, higher-ranking title.
-
D.
titleHolderPrecedence
Indicates the ordering or ranking of multiple title holders relative to one another in terms of precedence.
-
E.
titleHolderBeforeOtherTitle
Indicates that one entity held a particular title before another entity held a (possibly different) title.
- 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_69f34948adfc8190a937f1f622783c0b |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fea1f5d8c481908dc3351dc9ecef7f |
completed | May 9, 2026, 2:54 a.m. |
| PD | Predicate disambiguation | batch_69fea06b6fe0819095bf4c1bc9809927 |
completed | May 9, 2026, 2:48 a.m. |
Created at: May 1, 2026, 1:20 a.m.