Triple

T34396656
Position Surface form Disambiguated ID Type / Status
Subject De’ek Wadápuš E882847 entity
Predicate protectionJustifiedBy P24667 FINISHED
Object Native American religious freedom 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: Native American religious freedom | Statement: [De’ek Wadápuš, protectionJustifiedBy, Native American religious freedom]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: protectionJustifiedBy
Context triple: [De’ek Wadápuš, protectionJustifiedBy, Native American religious freedom]
  • A. protectionReason chosen
    Indicates the justification or cause for which protection is provided or required in the relationship between entities.
  • B. evidenceOfProtection
    Indicates that something serves as proof or indication that protection or safeguarding is present or has occurred.
  • C. protectsRight
    Indicates that one entity safeguards, upholds, or defends the legal or moral rights of another entity.
  • D. justificationUsedBy
    Indicates that a particular justification is employed or relied upon by a given entity (such as a person, system, or decision).
  • E. providesProtectionAgainst
    Indicates that one entity serves to guard, shield, or defend another entity from a specified harm, threat, or adverse effect.
  • 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_69f349c1304081909331872829e38106 completed April 30, 2026, 12:23 p.m.
NER Named-entity recognition batch_69f728a345488190bd7e6751b09ac591 completed May 3, 2026, 10:51 a.m.
PD Predicate disambiguation batch_69f7283ef2608190a7a85d7e7f5332c0 completed May 3, 2026, 10:49 a.m.
Created at: May 1, 2026, 1:59 a.m.