Triple
T25796081
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rosebery family |
E649685
|
entity |
| Predicate | hereditaryTitleCreated |
P31263
|
FINISHED |
| Object | Earl of Rosebery, 1703 |
—
|
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: Earl of Rosebery, 1703 | Statement: [Rosebery family, hereditaryTitleCreated, Earl of Rosebery, 1703]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hereditaryTitleCreated Context triple: [Rosebery family, hereditaryTitleCreated, Earl of Rosebery, 1703]
-
A.
aristocraticTitleCreatedFrom
Indicates that an aristocratic title originates from, or was formally established based on, another specified source title or entity.
-
B.
hereditaryTitleFor
Indicates that one entity is a hereditary title that is held by, or associated with, another entity, typically passed down through a family line.
-
C.
nobleTitleGranted
Indicates that a noble title has been formally conferred upon an entity by an authorized grantor or authority.
-
D.
nobleTitleHeirTo
Indicates that one entity is the designated heir to the noble title held by another entity.
-
E.
nobleTitleCreationDate
chosen
Indicates the date on which a particular noble title was formally created or granted.
- 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_69e7ab34f8c8819099f6c4dabdabf129 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f5ffc74fa481909b4fe24a9337f9eb |
completed | May 2, 2026, 1:44 p.m. |
| PD | Predicate disambiguation | batch_69f4938b960081909b53c074a3e0c7c2 |
completed | May 1, 2026, 11:50 a.m. |
Created at: April 22, 2026, 6:30 a.m.