Triple

T1186353
Position Surface form Disambiguated ID Type / Status
Subject Judas Iscariot E25255 entity
Predicate causeOfDeathAccordingToActs P144 FINISHED
Object falling headlong and bursting open 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: falling headlong and bursting open | Statement: [Judas Iscariot, causeOfDeathAccordingToActs, falling headlong and bursting open]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: causeOfDeathAccordingToActs
Context triple: [Judas Iscariot, causeOfDeathAccordingToActs, falling headlong and bursting open]
  • A. causeOfDeath chosen
    Indicates the specific factor, event, or condition that directly resulted in an entity’s death.
  • B. deathToll
    Indicates the number of deaths resulting from a particular event, situation, or cause.
  • C. associatedWithDeathOf
    Indicates a relationship where one entity is connected in some relevant way to the death of another entity, such as by involvement, causation, or contextual association.
  • D. fatalitiesCategory
    Indicates the classification of deaths associated with an event, incident, or condition into a specific category or severity level.
  • E. deathTollEstimate
    Indicates an estimated number of deaths attributed to a particular event, cause, or period.
  • 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_69a49427d98881908646d6c63b8cea1e completed March 1, 2026, 7:31 p.m.
NER Named-entity recognition batch_69a4bd53e4b48190abb2167f8074a6bc completed March 1, 2026, 10:27 p.m.
PD Predicate disambiguation batch_69a4bb59ca6c81908597a81646674aaa completed March 1, 2026, 10:19 p.m.
Created at: March 1, 2026, 7:45 p.m.