Triple
T2024697
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | San Francisco Platform (1976) |
E44181
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | religious policy statement |
C8015
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: religious policy statement Context triple: [San Francisco Platform (1976), instanceOf, religious policy statement]
-
A.
religious policy change
A religious policy change is a deliberate alteration in the rules, doctrines, or practices governing religious institutions or state-religion relations, typically enacted to address evolving social, political, or cultural conditions.
-
B.
declaration on religious freedom
A declaration on religious freedom is an official statement or document that affirms and protects individuals’ rights to hold, practice, change, or abstain from religious beliefs without coercion or discrimination.
-
C.
religious freedom law
Religious freedom law is a legal framework that protects individuals’ and groups’ rights to hold, practice, change, or abstain from religious beliefs without undue interference or discrimination by the state or others.
-
D.
religious sphere
The religious sphere is the domain of social life in which beliefs, rituals, institutions, and practices related to the sacred or transcendent are created, maintained, and contested.
-
E.
religious freedom report
A religious freedom report is a document that systematically evaluates and describes the status, protections, violations, and trends related to individuals’ and groups’ rights to practice, change, or abstain from religion within a specific country or region.
- F. None of above. chosen
Provenance (1 batch)
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_69a8891201bc8190aca837be6de41579 |
completed | March 4, 2026, 7:33 p.m. |
Created at: March 4, 2026, 7:38 p.m.