Triple

T30895632
Position Surface form Disambiguated ID Type / Status
Subject Keats’ grave with inscription "Here lies One Whose Name was writ in Water" E787012 entity
Predicate buriedPersonCauseOfDeath P144 FINISHED
Object tuberculosis 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: tuberculosis | Statement: [Keats’ grave with inscription "Here lies One Whose Name was writ in Water", buriedPersonCauseOfDeath, tuberculosis]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: buriedPersonCauseOfDeath
Context triple: [Keats’ grave with inscription "Here lies One Whose Name was writ in Water", buriedPersonCauseOfDeath, tuberculosis]
  • A. causeOfDeath chosen
    Indicates the specific factor, event, or condition that directly resulted in an entity’s death.
  • B. reasonForDeath
    Indicates the cause, circumstance, or condition that led to an entity’s death.
  • C. buriedPersonDeathYear
    Indicates the year in which the person who is buried (at a given burial site) died.
  • D. deathCharacteristic
    Indicates a characteristic, attribute, or quality specifically associated with a death event or the manner in which death occurred.
  • E. deathDetails
    Indicates the specific circumstances, causes, and contextual information associated with an entity’s death.
  • 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_69f6abaa1f648190b77073771df3bf3b completed May 3, 2026, 1:58 a.m.
PD Predicate disambiguation batch_69f6aa1e84b88190b025f6ca40f17a8a completed May 3, 2026, 1:51 a.m.
Created at: April 29, 2026, 8:49 p.m.