Triple
T38617479
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John Russell, 1st Earl of Bedford |
E936771
|
entity |
| Predicate | dateOfCreationOfEarldom |
P100550
|
FINISHED |
| Object | 1550 |
—
|
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: 1550 | Statement: [John Russell, 1st Earl of Bedford, dateOfCreationOfEarldom, 1550]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dateOfCreationOfEarldom Context triple: [John Russell, 1st Earl of Bedford, dateOfCreationOfEarldom, 1550]
-
A.
yearOfCreationOfEarldom
chosen
Indicates the specific year in which a particular earldom was formally created or established.
-
B.
creationOfDukedomDate
Indicates the date on which a particular dukedom was formally created or established.
-
C.
monarchDuringCreationOfLinkedEarldom
Indicates that the subject was the reigning monarch at the time when the referenced earldom was created.
-
D.
createdEarlOfNottinghamDate
Indicates the date on which the title of Earl of Nottingham was created or conferred.
-
E.
createdEarlOfNorthumberland
Indicates that an entity conferred or established the title of Earl of Northumberland upon another 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_69f76ed403208190b862dc795171353f |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fe7bfc94bc81909eeec946e8c1c450 |
completed | May 9, 2026, 12:12 a.m. |
| PD | Predicate disambiguation | batch_69fe7b74a1188190886f128e07f712da |
completed | May 9, 2026, 12:10 a.m. |
Created at: May 3, 2026, 4:32 p.m.