Triple
T6740367
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Akhbari |
E154063
|
entity |
| Predicate | viewOnQiyas |
P26536
|
FINISHED |
| Object | rejects analogical reasoning (qiyas) |
—
|
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: rejects analogical reasoning (qiyas) | Statement: [Akhbari, viewOnQiyas, rejects analogical reasoning (qiyas)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: viewOnQiyas Context triple: [Akhbari, viewOnQiyas, rejects analogical reasoning (qiyas)]
-
A.
viewOnAnalogy
Indicates a relationship where one entity interprets, understands, or evaluates another entity by drawing an analogy to something else.
-
B.
attitudeToQiyas
chosen
Indicates the stance or position an entity holds toward the use or validity of qiyas (analogical reasoning).
-
C.
viewOnReason
Indicates that one entity holds or expresses a particular opinion, stance, or perspective about a specified reason or justification.
-
D.
viewOnSin
Indicates a person's stance, opinion, or doctrinal position regarding what constitutes sin or sinful behavior.
-
E.
viewOnValue
Indicates a relationship where one entity holds or expresses a particular perspective, opinion, or stance regarding a specific value or principle.
- 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_69c6880d84d8819095d19de2295f26ac |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d18971e081908372cd25d52a11bd |
completed | March 27, 2026, 6:50 p.m. |
| PD | Predicate disambiguation | batch_69c6d09067a0819087ed6c820f4699f8 |
completed | March 27, 2026, 6:46 p.m. |
Created at: March 27, 2026, 2:10 p.m.