Triple
T32020259
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Earl of Darnley |
E817662
|
entity |
| Predicate | notableBearerDeath |
P206146
|
FINISHED |
| Object | Henry Stuart, Lord Darnley |
E211336
|
NE 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: Henry Stuart, Lord Darnley | Statement: [Earl of Darnley, notableBearerDeath, Henry Stuart, Lord Darnley]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableBearerDeath Context triple: [Earl of Darnley, notableBearerDeath, Henry Stuart, Lord Darnley]
-
A.
notableBearerDeathYear
Indicates the year in which a notable bearer of the referenced name, title, or role died.
-
B.
notableDeath
Indicates that an entity’s death is considered significant or noteworthy in some context.
-
C.
notableDeathMethod
Indicates the manner or method by which an entity (typically a person) died, especially when that cause of death is historically or culturally notable.
-
D.
notablePersonKilledThere
Indicates that a notable or famous person was killed at the referenced location.
-
E.
notablePersonDiedHere
Indicates that a notable or famous person died at the referenced location.
- F. None of above. chosen
Provenance (5 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_69f348fb04e4819081f4eab040ed7959 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a037c9141dc819098d7fcc36e69882c |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2eddd6b9808190ae845a9587bc193c |
completed | June 14, 2026, 4:59 p.m. |
| PD | Predicate disambiguation | batch_6a0379eaa540819095a1c5d9f3513f9b |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c7fb9f88190b384b1b68200aef0 |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 1, 2026, 12:16 a.m.