Triple
T30895630
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Keats’ grave with inscription "Here lies One Whose Name was writ in Water" |
E787012
|
entity |
| Predicate | buriedPersonBirthYear |
P171604
|
FINISHED |
| Object | 1795 |
—
|
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: 1795 | Statement: [Keats’ grave with inscription "Here lies One Whose Name was writ in Water", buriedPersonBirthYear, 1795]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: buriedPersonBirthYear Context triple: [Keats’ grave with inscription "Here lies One Whose Name was writ in Water", buriedPersonBirthYear, 1795]
-
A.
buriedPersonFullName
Indicates that one entity is the full name of a person who is buried, typically used to identify the individual interred at a burial site.
-
B.
buriedPersonNationality
Indicates the nationality of the person who is buried.
-
C.
originallyInterredPerson
Indicates that one entity is the person who was first buried or laid to rest at the location or in the grave represented by the other entity.
-
D.
dateOfBurial
Indicates the specific date on which an entity was buried.
-
E.
deathYearInvestigated
Indicates that an entity’s year of death has been the subject of investigation or inquiry.
- 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_69f224bcbcb48190836df847424e4057 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6a1ac56b88190a820434b65c9fa23 |
completed | May 3, 2026, 1:15 a.m. |
| PD | Predicate disambiguation | batch_69f69fe463248190aa78128abeab1183 |
completed | May 3, 2026, 1:07 a.m. |
| PDg | Predicate description generation | batch_69f6a0e920cc8190a943fdd0594906c5 |
completed | May 3, 2026, 1:12 a.m. |
Created at: April 29, 2026, 8:49 p.m.