Triple
T5056114
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sunni fiqh |
E113906
|
entity |
| Predicate | normativelyGuides |
P12028
|
FINISHED |
| Object | Muslim personal behavior |
—
|
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: Muslim personal behavior | Statement: [Sunni fiqh, normativelyGuides, Muslim personal behavior]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: normativelyGuides Context triple: [Sunni fiqh, normativelyGuides, Muslim personal behavior]
-
A.
normativeFor
chosen
Indicates that something establishes, prescribes, or encodes the norms, standards, or rules that should govern another thing’s behavior or state.
-
B.
providesGuidanceTo
Indicates that one entity offers direction, advice, or instruction to another entity.
-
C.
normativeGoal
Indicates that one entity is a desired or prescribed objective, standard, or end state that another entity ought to pursue or realize.
-
D.
guidanceType
Indicates the specific kind or category of guidance being provided or referenced in the relationship between entities.
-
E.
levelOfNorm
Indicates the degree or extent to which something conforms to a specified norm, standard, or expected behavior.
- 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_69bd443aa1f88190abb992d138f2cf42 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd744e45588190beaa2f96bb2f41e2 |
completed | March 20, 2026, 4:22 p.m. |
| PD | Predicate disambiguation | batch_69bd715479f08190933604aebd34414f |
completed | March 20, 2026, 4:09 p.m. |
Created at: March 20, 2026, 1:38 p.m.