Triple
T25177061
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Richard John Bingham, 7th Earl of Lucan |
E630476
|
entity |
| Predicate | deathDeclared |
P84455
|
FINISHED |
| Object | 2016 |
—
|
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: 2016 | Statement: [Richard John Bingham, 7th Earl of Lucan, deathDeclared, 2016]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: deathDeclared Context triple: [Richard John Bingham, 7th Earl of Lucan, deathDeclared, 2016]
-
A.
deathClaim
Indicates that a claim has been made asserting or reporting the death of a particular entity.
-
B.
deathStatus
Indicates whether an entity is alive, dead, or in another specified state related to mortality.
-
C.
deathResult
Indicates that one event, condition, or action leads to or causes the death of an entity.
-
D.
deathBy
Indicates a relationship where one entity’s death is caused by another entity, event, or factor.
-
E.
deathAnnouncedBy
chosen
Indicates that the occurrence of a death is publicly communicated or formally reported by a specific agent or source.
- 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_69e75a88fdf081908e47ae6e195c14e1 |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f46dc1ddd0819089722f45adc50d84 |
completed | May 1, 2026, 9:09 a.m. |
| PD | Predicate disambiguation | batch_69f44d8043b081908bbffd7f044b4f26 |
completed | May 1, 2026, 6:51 a.m. |
Created at: April 21, 2026, 12:34 p.m.