Triple

T61160
Position Surface form Disambiguated ID Type / Status
Subject Free Exercise Clause E1214 entity
Predicate protectsAgainst P1040 FINISHED
Object undue government interference with religious practice 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: undue government interference with religious practice | Statement: [Free Exercise Clause, protectsAgainst, undue government interference with religious practice]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: protectsAgainst
Context triple: [Free Exercise Clause, protectsAgainst, undue government interference with religious practice]
  • A. protects chosen
    Indicates taking action to keep someone or something safe from harm, danger, or negative effects.
  • B. protectedBy
    Indicates that one entity provides protection, defense, or safeguarding for another entity.
  • C. isProtectedBy
    Indicates that one entity provides protection, defense, or safeguarding for another entity.
  • D. protectedIn
    Indicates that one entity is safeguarded, preserved, or kept safe within the context, environment, or jurisdiction of another entity.
  • E. ensures
    Indicates that one entity guarantees or makes certain that a particular condition, outcome, or state holds for another entity or situation.
  • 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_69a24ba4f760819081f6638a3c70538a completed Feb. 28, 2026, 1:57 a.m.
NER Named-entity recognition batch_69a251a1b8ac8190b44be4c3c41e5681 completed Feb. 28, 2026, 2:23 a.m.
PD Predicate disambiguation batch_69a24ea0bec48190b2af1fb287e9e692 completed Feb. 28, 2026, 2:10 a.m.
Created at: Feb. 28, 2026, 2:02 a.m.