Triple
T30308609
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Edward Lascelles, 1st Earl of Harewood |
E770858
|
entity |
| Predicate | createdBaronHarewood |
P39376
|
FINISHED |
| Object | 1796 |
—
|
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: 1796 | Statement: [Edward Lascelles, 1st Earl of Harewood, createdBaronHarewood, 1796]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: createdBaronHarewood Context triple: [Edward Lascelles, 1st Earl of Harewood, createdBaronHarewood, 1796]
-
A.
createdBaronet
Indicates that one entity formally established or granted a baronetcy title to another entity.
-
B.
createdBaronOrBaronessOf
chosen
Indicates that one entity granted or established the noble title of baron or baroness for another entity.
-
C.
createdMarquess
Indicates that one entity formally established or granted the noble title of marquess to another entity.
-
D.
successorAsBaronLatimer
Indicates that one entity became the next holder of the title Baron Latimer after another entity.
-
E.
dateOfBaronetcy
Indicates the date on which a person was granted or created a baronetcy title.
- 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_69f22488f224819081b0f3ec41ab975c |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fdfbafe32081909c62653ff4fc155c |
completed | May 8, 2026, 3:05 p.m. |
| PD | Predicate disambiguation | batch_69fdf64db4a881908f8250e24ae3cefb |
completed | May 8, 2026, 2:42 p.m. |
Created at: April 29, 2026, 7:49 p.m.