Triple
T6424239
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baron Cavendish of Hardwick |
E128017
|
entity |
| Predicate | isAristocraticTitle |
P20790
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Baron Cavendish of Hardwick, isAristocraticTitle, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isAristocraticTitle Context triple: [Baron Cavendish of Hardwick, isAristocraticTitle, true]
-
A.
aristocraticTitleIn
Indicates that an entity holds or is associated with a specific aristocratic or noble title within a particular jurisdiction or context.
-
B.
isRoyalTitle
Indicates that something is a formal title associated with royalty or a royal rank.
-
C.
nobleTitleFrom
Indicates that a person derives or holds their noble title from a specified source, such as a place, lineage, or authority.
-
D.
aristocraticRole
chosen
Indicates that an entity holds or is associated with a formal position, title, or function within an aristocratic or noble hierarchy.
-
E.
aristocraticTitleBeforeMarriage
Indicates that the subject held a specific aristocratic title prior to entering into marriage.
- 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_69c00838de888190af2eec0b80495efa |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c06906eea88190a445c1ff1169c2b1 |
completed | March 22, 2026, 10:11 p.m. |
| PD | Predicate disambiguation | batch_69c060f780b08190aa650b4d1fc51f21 |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:43 p.m.