Triple
T5361593
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Salar |
E103032
|
entity |
| Predicate | associatedReligionLaw |
P6259
|
FINISHED |
| Object | 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: Islamic law | Statement: [Salar, associatedReligionLaw, Islamic law]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedReligionLaw Context triple: [Salar, associatedReligionLaw, Islamic law]
-
A.
religiousJurisdiction
Indicates that one entity holds official religious authority or governance over another entity or area.
-
B.
religionPolicy
Indicates the stance, rules, or approach an entity adopts toward religious beliefs, practices, or institutions.
-
C.
legalStatusOfReligion
chosen
Indicates the formal legal standing, recognition, and regulatory conditions of a religion within a given jurisdiction or political entity.
-
D.
associatedReligionText
Indicates that there is a textual work (such as a scripture or religious document) that is specifically associated with, or pertains to, a given religion.
-
E.
associatedReligionInTexts
Indicates that a particular religion is mentioned or linked in written texts in connection with the given 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_69bd43daa3e4819090b59d127db70e57 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd865a0bb081909579cfe7c7974075 |
completed | March 20, 2026, 5:39 p.m. |
| PD | Predicate disambiguation | batch_69bd845f41f88190b75b8b64b9e41862 |
completed | March 20, 2026, 5:31 p.m. |
Created at: March 20, 2026, 2:02 p.m.