Triple
T33244105
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Robert Henley, 1st Earl of Northington |
E851045
|
entity |
| Predicate | createdEarlOfNorthington |
P198885
|
FINISHED |
| Object | 1764 |
—
|
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: 1764 | Statement: [Robert Henley, 1st Earl of Northington, createdEarlOfNorthington, 1764]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: createdEarlOfNorthington Context triple: [Robert Henley, 1st Earl of Northington, createdEarlOfNorthington, 1764]
-
A.
createdEarlOfNorthampton
Indicates that a person was granted or elevated to the noble title of Earl of Northampton.
-
B.
createdEarlOfNorthumberland
Indicates that an entity conferred or established the title of Earl of Northumberland upon another entity.
-
C.
createdEarlOfNottinghamDate
Indicates the date on which the title of Earl of Nottingham was created or conferred.
-
D.
createdEarlOfHarewood
Indicates the act of granting or establishing the noble title "Earl of Harewood" for a person.
-
E.
createdEarlOfWestmorlandBy
Indicates that a person or authority conferred or established the title "Earl of Westmorland" upon a specific individual.
- F. None of above. chosen
Provenance (4 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_69f34962386c81909ddc3bf9e18ddeb8 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69ff109695008190a22b47ef8be2e3f9 |
completed | May 9, 2026, 10:46 a.m. |
| PD | Predicate disambiguation | batch_69ff0f243ea88190970d2c520b55c816 |
completed | May 9, 2026, 10:40 a.m. |
| PDg | Predicate description generation | batch_69ff10956d3881909144f880f92e90c4 |
completed | May 9, 2026, 10:46 a.m. |
Created at: May 1, 2026, 1:31 a.m.