Triple
T5167981
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Guardian Council |
E116604
|
entity |
| Predicate | religiousStandard |
P2330
|
FINISHED |
| Object | Shia Islamic law |
—
|
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: Shia Islamic law | Statement: [Guardian Council, religiousStandard, Shia Islamic law]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: religiousStandard Context triple: [Guardian Council, religiousStandard, Shia Islamic law]
-
A.
religiousElement
Indicates that something is a component, aspect, or feature associated with a religion or religious practice.
-
B.
religiousCanon
Indicates that something is formally recognized as part of an established body of authoritative religious texts or doctrine.
-
C.
religiousTarget
Indicates that an action, policy, or behavior is directed at someone or something specifically because of their religion or religious affiliation.
-
D.
religiousTopicAddressed
Indicates that a subject deals with, discusses, or focuses on a religious theme, issue, or question.
-
E.
religiousFunction
chosen
Indicates that one entity serves a religious role, purpose, or function in relation to another entity.
- 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_69bd445ff97c81909a2615cc56235470 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd794b87508190be3b82726ef4b37c |
completed | March 20, 2026, 4:43 p.m. |
| PD | Predicate disambiguation | batch_69bd77b36c008190b91011a9fa52b3d2 |
completed | March 20, 2026, 4:37 p.m. |
Created at: March 20, 2026, 1:45 p.m.