Triple

T18654819
Position Surface form Disambiguated ID Type / Status
Subject Saint Gervasius and Saint Protasius E456030 entity
Predicate martyrdomType P92138 FINISHED
Object beheading (traditional account) 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: beheading (traditional account) | Statement: [Saint Gervasius and Saint Protasius, martyrdomType, beheading (traditional account)]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: martyrdomType
Context triple: [Saint Gervasius and Saint Protasius, martyrdomType, beheading (traditional account)]
  • A. martyrdomStatus
    Indicates the state or condition of an entity with respect to being recognized or regarded as a martyr.
  • B. martyrdomMethod chosen
    Indicates the method or means by which an individual becomes a martyr (i.e., how the martyrdom is carried out).
  • C. martyr
    Indicates that an entity is killed or suffers greatly, typically for a belief, cause, or principle, often being regarded or treated as a martyr as a result.
  • D. martyrdomContext
    Indicates the circumstances or situational factors under which an entity becomes a martyr or is regarded as having undergone martyrdom.
  • E. martyredUnder
    Indicates that an entity was killed or executed as a martyr during the rule, authority, or actions of another entity.
  • 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_69d8d38ea1e88190997e9b231190ba6f completed April 10, 2026, 10:40 a.m.
NER Named-entity recognition batch_69e55084012881909b9dd60565011c86 completed April 19, 2026, 10 p.m.
PD Predicate disambiguation batch_69e478d85864819093cbad5ed9b54878 completed April 19, 2026, 6:40 a.m.
Created at: April 10, 2026, 11:47 a.m.