Triple
T30895620
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Keats’ grave with inscription "Here lies One Whose Name was writ in Water" |
E787012
|
entity |
| Predicate | epitaphTone |
P165524
|
FINISHED |
| Object | self-effacing |
—
|
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: self-effacing | Statement: [Keats’ grave with inscription "Here lies One Whose Name was writ in Water", epitaphTone, self-effacing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: epitaphTone Context triple: [Keats’ grave with inscription "Here lies One Whose Name was writ in Water", epitaphTone, self-effacing]
-
A.
hasEpitaph
Indicates that an entity has a specific epitaph inscribed or associated with it.
-
B.
toneOfEulogy
chosen
Indicates the emotional tone or mood conveyed by a eulogy.
-
C.
isPosthumousTributeTo
Indicates that something (such as a work, event, or honor) is created or given as a tribute to a person after that person has died.
-
D.
epigraphicType
Indicates the specific kind or category of an inscription as classified in epigraphic studies.
-
E.
memorialInscription
Indicates that a text is inscribed on a memorial object to commemorate a person, event, or occasion.
- 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_69f224bcbcb48190836df847424e4057 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6923baa1081909407a75d6c22a34f |
completed | May 3, 2026, 12:09 a.m. |
| PD | Predicate disambiguation | batch_69f68b7ec098819080480998038de940 |
completed | May 2, 2026, 11:40 p.m. |
Created at: April 29, 2026, 8:49 p.m.