Triple

T31401927
Position Surface form Disambiguated ID Type / Status
Subject Stockholms blodbad E801016 entity
Predicate justificationClaimedAs P130462 FINISHED
Object punishment for alleged heresy 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: punishment for alleged heresy | Statement: [Stockholms blodbad, justificationClaimedAs, punishment for alleged heresy]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: justificationClaimedAs
Context triple: [Stockholms blodbad, justificationClaimedAs, punishment for alleged heresy]
  • A. claimedJustificationAs chosen
    Indicates that one entity presents another entity as the reason or rationale supporting its claim, action, or position.
  • B. claimedAs
    Indicates that one entity asserts ownership, authorship, responsibility, or some other form of association over another entity.
  • C. claimedIn
    Indicates that a statement, fact, or assertion is reported or documented within a particular source, document, or claim.
  • D. claimedFor
    Indicates that one entity has asserted ownership, responsibility, or entitlement over or on behalf of another entity.
  • E. alsoClaimedBy
    Indicates that the same item, statement, or resource is asserted or claimed by an additional party besides the primary one.
  • 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_69f224ea9998819086ae2e4f4f4091c8 completed April 29, 2026, 3:34 p.m.
NER Named-entity recognition batch_69f6a5f71b2c8190aade8a83f465be0c completed May 3, 2026, 1:33 a.m.
PD Predicate disambiguation batch_69f69fe66df08190958558d63ee623d9 completed May 3, 2026, 1:07 a.m.
Created at: April 29, 2026, 9:20 p.m.