Triple

T22659284
Position Surface form Disambiguated ID Type / Status
Subject The Meritorious Price of Our Redemption E559617 entity
Predicate censorshipAction P142663 FINISHED
Object publicly burned in Boston 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: publicly burned in Boston | Statement: [The Meritorious Price of Our Redemption, censorshipAction, publicly burned in Boston]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: censorshipAction
Context triple: [The Meritorious Price of Our Redemption, censorshipAction, publicly burned in Boston]
  • A. censorshipTarget
    Indicates that an entity is the object or focus of censorship by another entity or authority.
  • B. censorshipEvent
    Indicates an event in which information, expression, or communication is suppressed, restricted, or altered by some controlling authority or mechanism.
  • C. censorshipReason
    Indicates the justification or cause given for why certain content is suppressed, restricted, or removed.
  • D. censorshipStatusChange
    Indicates a change in an entity’s censorship state, such as being newly censored, uncensored, or having its censorship level modified.
  • E. typeOfCensorship chosen
    Indicates the specific kind or method of censorship being applied in a given context.
  • 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_69e2454a158c819093b8e35f5045efb6 completed April 17, 2026, 2:35 p.m.
NER Named-entity recognition batch_69f1765dc9088190b022ac564a8b5c26 completed April 29, 2026, 3:09 a.m.
PD Predicate disambiguation batch_69ee6294c4c08190b7e4829f4b9af24b completed April 26, 2026, 7:08 p.m.
Created at: April 17, 2026, 3:07 p.m.