Triple
T27330949
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Archibald Primrose, 1st Earl of Rosebery |
E689796
|
entity |
| Predicate | createdPeerageTitleDate |
P2735
|
FINISHED |
| Object | 1828 |
—
|
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: 1828 | Statement: [Archibald Primrose, 1st Earl of Rosebery, createdPeerageTitleDate, 1828]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: createdPeerageTitleDate Context triple: [Archibald Primrose, 1st Earl of Rosebery, createdPeerageTitleDate, 1828]
-
A.
nobleTitleCreationDate
Indicates the date on which a particular noble title was formally created or granted.
-
B.
peerageCreated
Indicates that a noble title or rank within a peerage system has been formally established or conferred.
-
C.
dateOfElevationToPeerage
chosen
Indicates the specific date on which an individual was formally elevated to a rank of nobility or peerage.
-
D.
dateOfCreationAsMarquess
Indicates the specific date on which a person was created or elevated to the rank or title of marquess.
-
E.
aristocraticTitleCreatedFrom
Indicates that an aristocratic title originates from, or was formally established based on, another specified source title or 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_69ef355d4cb08190ab032c0a2e7d3753 |
completed | April 27, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69f7431c0eec81909ead443e07d75e18 |
completed | May 3, 2026, 12:44 p.m. |
| PD | Predicate disambiguation | batch_69f74143cf708190a12d487884298437 |
completed | May 3, 2026, 12:36 p.m. |
Created at: April 27, 2026, 11:38 a.m.