Triple
T31099200
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | الحِجْر |
E792622
|
entity |
| Predicate | fiqhStatus |
P36007
|
FINISHED |
| Object | له أحكام خاصة في الفقه الإسلامي |
—
|
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: له أحكام خاصة في الفقه الإسلامي | Statement: [الحِجْر, fiqhStatus, له أحكام خاصة في الفقه الإسلامي]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fiqhStatus Context triple: [الحِجْر, fiqhStatus, له أحكام خاصة في الفقه الإسلامي]
-
A.
fiqhScope
Indicates the domain or scope within Islamic jurisprudence (fiqh) to which a particular ruling, issue, or concept applies.
-
B.
fiqh
Indicates the relationship of deriving, applying, or adhering to Islamic legal rulings and jurisprudential judgments regarding actions or situations.
-
C.
hasRulingInFiqh
chosen
Indicates that a subject has an associated legal ruling or judgment within the framework of Islamic jurisprudence (fiqh).
-
D.
statusInIslamicTradition
Indicates the recognized standing, role, or level of esteem an entity holds within Islamic religious, cultural, or scholarly tradition.
-
E.
quranicStatus
Indicates the status or classification of something in relation to its recognition, treatment, or role within the Quran.
- 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_69f224cf157c81909e2d2bd88c9282c3 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69c234d648190a243fb2b107136a9 |
completed | May 3, 2026, 12:51 a.m. |
| PD | Predicate disambiguation | batch_69f69665cd9c819088c388fc82fec42e |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 29, 2026, 9:03 p.m.