Triple

T3152796
Position Surface form Disambiguated ID Type / Status
Subject Aleinu E65913 entity
Predicate censorshipHistory P17134 FINISHED
Object some phrases historically censored in Christian lands 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: some phrases historically censored in Christian lands | Statement: [Aleinu, censorshipHistory, some phrases historically censored in Christian lands]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: censorshipHistory
Context triple: [Aleinu, censorshipHistory, some phrases historically censored in Christian lands]
  • A. censorshipStatusAtTime
    Indicates the censorship status of something at a specific point in time, capturing whether and how it was censored then.
  • B. hasCensorshipHistory chosen
    Indicates that an entity has previously been subject to censorship or involved in acts of censoring content.
  • C. censorshipYear
    Indicates the year in which an act of censorship was imposed on the referenced content or entity.
  • D. revisedVersionCensorshipStatus
    Indicates the censorship or restriction status applied to a revised version of some original content.
  • E. censorshipReason
    Indicates the justification or cause given for why certain content is suppressed, restricted, or removed.
  • 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_69ad8584485081909ed529e890cadc4a completed March 8, 2026, 2:19 p.m.
NER Named-entity recognition batch_69ada5c27258819099c46a657779780b completed March 8, 2026, 4:37 p.m.
PD Predicate disambiguation batch_69ad9dfbf0348190952a6bca8fc5fed1 completed March 8, 2026, 4:04 p.m.
Created at: March 8, 2026, 3:05 p.m.