Triple
T1918841
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yazidism |
E40078
|
entity |
| Predicate | hasReligiousLawFeature |
P6166
|
FINISHED |
| Object | purity rules |
—
|
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: purity rules | Statement: [Yazidism, hasReligiousLawFeature, purity rules]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasReligiousLawFeature Context triple: [Yazidism, hasReligiousLawFeature, purity rules]
-
A.
religiousJurisdiction
Indicates that one entity holds official religious authority or governance over another entity or area.
-
B.
legalStatusOfReligion
Indicates the formal legal standing, recognition, and regulatory conditions of a religion within a given jurisdiction or political entity.
-
C.
hasReligiousOrigin
Indicates that something originates from, is derived from, or is fundamentally based on a religious tradition, belief system, or practice.
-
D.
hasAssociatedReligion
Indicates that an entity is connected with or linked to a particular religion.
-
E.
religiousRestriction
chosen
Indicates that one entity imposes, experiences, or is subject to limitations or rules based on religious beliefs or practices in relation to another entity or 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_69a8864298748190a2f2fd34f7ef8d77 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb211eda88190865de7a0522a453d |
completed | March 7, 2026, 5:05 a.m. |
| PD | Predicate disambiguation | batch_69abafed2ab481908920334e77b1021b |
completed | March 7, 2026, 4:56 a.m. |
Created at: March 4, 2026, 7:35 p.m.