Triple
T33008987
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brudenell-Bruce |
E844587
|
entity |
| Predicate | hereditaryTitles |
P127258
|
FINISHED |
| Object | marquessate |
—
|
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: marquessate | Statement: [Brudenell-Bruce, hereditaryTitles, marquessate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hereditaryTitles Context triple: [Brudenell-Bruce, hereditaryTitles, marquessate]
-
A.
hereditaryTitleInheritance
Indicates that a hereditary title is passed from one individual to another according to established rules of succession.
-
B.
hereditaryPeerage
Indicates that a person holds a noble title that is legally inheritable and passes down through family lineage.
-
C.
hereditaryTitleFor
chosen
Indicates that one entity is a hereditary title that is held by, or associated with, another entity, typically passed down through a family line.
-
D.
nobleTitleHeirTo
Indicates that one entity is the designated heir to the noble title held by another entity.
-
E.
aristocraticTitleIn
Indicates that an entity holds or is associated with a specific aristocratic or noble title within a particular jurisdiction or context.
- 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_69f3494e59f08190b9127c693e5c7e8f |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d74b20a48190900dda1014cc13a8 |
completed | May 3, 2026, 5:04 a.m. |
| PD | Predicate disambiguation | batch_69f6d26f27dc8190ae426a3e1573933e |
completed | May 3, 2026, 4:43 a.m. |
Created at: May 1, 2026, 1:23 a.m.