Triple

T14799276
Position Surface form Disambiguated ID Type / Status
Subject Heraclius (chamberlain) E347862 entity
Predicate fateAfterEvent P3146 FINISHED
Object killed shortly after Valentinian III’s assassination 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: killed shortly after Valentinian III’s assassination | Statement: [Heraclius (chamberlain), fateAfterEvent, killed shortly after Valentinian III’s assassination]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: fateAfterEvent
Context triple: [Heraclius (chamberlain), fateAfterEvent, killed shortly after Valentinian III’s assassination]
  • A. fate chosen
    Indicates that an entity is destined or predetermined to experience a particular outcome or course of events beyond its control.
  • B. eventualFate
    Indicates the ultimate outcome or final state that an entity is destined to reach over time.
  • C. afterlifeFate
    Indicates the outcome or condition an entity experiences in the afterlife as a result of its life or actions.
  • D. facedEvent
    Indicates that an entity directly encountered, experienced, or dealt with a particular event.
  • E. capitalAfterEvent
    Indicates that a location became the capital of a political or administrative entity as a result of, or following, a specific event.
  • 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_69d822ea8b7c819097dfadf3d45545e6 completed April 9, 2026, 10:06 p.m.
NER Named-entity recognition batch_69decd6131f08190885f1d27b4bfac7a completed April 14, 2026, 11:27 p.m.
PD Predicate disambiguation batch_69de8c090d1081909b5a9bf437499d6c completed April 14, 2026, 6:48 p.m.
Created at: April 10, 2026, 1:31 a.m.