Triple

T611030
Position Surface form Disambiguated ID Type / Status
Subject Nero E12097 entity
Predicate deathCircumstances P144 FINISHED
Object committed suicide after being declared a public enemy by the Senate 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: committed suicide after being declared a public enemy by the Senate | Statement: [Nero, deathCircumstances, committed suicide after being declared a public enemy by the Senate]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: deathCircumstances
Context triple: [Nero, deathCircumstances, committed suicide after being declared a public enemy by the Senate]
  • A. causeOfDeath chosen
    Indicates the specific factor, event, or condition that directly resulted in an entity’s death.
  • B. death
    Indicates the event or state in which an entity ceases to live or exist, marking the end of its biological or functional processes.
  • C. placeOfDeath
    Indicates the location where an entity (typically a person or animal) died.
  • D. diedWhile
    Indicates that one entity ceased to live during the occurrence or performance of another specified event or activity.
  • E. deathToll
    Indicates the number of deaths resulting from a particular event, situation, or cause.
  • 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_69a493309df48190a327f748e88049a6 completed March 1, 2026, 7:27 p.m.
NER Named-entity recognition batch_69a49df7c088819082eb70de4f0f4fbf completed March 1, 2026, 8:13 p.m.
PD Predicate disambiguation batch_69a49cfa7b4481909bec7a5fd3e98c65 completed March 1, 2026, 8:09 p.m.
Created at: March 1, 2026, 7:35 p.m.