Triple
T33244104
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Robert Henley, 1st Earl of Northington |
E851045
|
entity |
| Predicate | createdBaronHenley |
P39376
|
FINISHED |
| Object | 1760 |
—
|
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: 1760 | Statement: [Robert Henley, 1st Earl of Northington, createdBaronHenley, 1760]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: createdBaronHenley Context triple: [Robert Henley, 1st Earl of Northington, createdBaronHenley, 1760]
-
A.
createdBaronOrBaronessOf
chosen
Indicates that one entity granted or established the noble title of baron or baroness for another entity.
-
B.
createdBaronet
Indicates that one entity formally established or granted a baronetcy title to another entity.
-
C.
createdDukeOfYorkBy
Indicates the action by which an authority or agent formally conferred or established the title of Duke of York upon a person.
-
D.
createdMarquess
Indicates that one entity formally established or granted the noble title of marquess to another entity.
-
E.
createdDukeOfLeinster
Indicates that one entity formally granted or established the title "Duke of Leinster" for 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_69f34962386c81909ddc3bf9e18ddeb8 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69ff0e9c75208190a4423261f00b79b3 |
completed | May 9, 2026, 10:38 a.m. |
| PD | Predicate disambiguation | batch_69ff0e07f08481909c4ae322632a6bf0 |
completed | May 9, 2026, 10:35 a.m. |
Created at: May 1, 2026, 1:31 a.m.