Triple

T23128981
Position Surface form Disambiguated ID Type / Status
Subject Arda-Mulissu E577114 entity
Predicate resultOfAssassinationPlot P23938 FINISHED
Object Esarhaddon’s accession to the throne 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: Esarhaddon’s accession to the throne | Statement: [Arda-Mulissu, resultOfAssassinationPlot, Esarhaddon’s accession to the throne]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: resultOfAssassinationPlot
Context triple: [Arda-Mulissu, resultOfAssassinationPlot, Esarhaddon’s accession to the throne]
  • A. consequenceOfAssassinationAttempt chosen
    Indicates a state, event, or condition that occurs as a direct result of an assassination attempt.
  • B. assassinationEvent
    Indicates a deliberate killing of a specific individual, typically for political or strategic reasons, carried out as a planned event.
  • C. assassinatedIn
    Indicates that an assassination of one entity occurred within the specified location or context represented by another entity.
  • D. relatedAssassination
    Indicates a relationship where one entity is connected to, involved in, or associated with an assassination event concerning another entity.
  • E. wasAssassinationTarget
    Indicates that an entity was the intended victim or objective of an assassination attempt.
  • 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_69e245f7b0e481909c473ff4e6a54e2c completed April 17, 2026, 2:38 p.m.
NER Named-entity recognition batch_69f18e857b40819081f9df03fff64d48 completed April 29, 2026, 4:52 a.m.
PD Predicate disambiguation batch_69ef89f83b108190aaaa1db6221fc163 completed April 27, 2026, 4:08 p.m.
Created at: April 17, 2026, 4 p.m.