Triple
T1296399
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Umrah |
E27661
|
entity |
| Predicate | jurisprudenceDiscussedIn |
P28367
|
FINISHED |
| Object | Islamic fiqh |
—
|
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 fiqh | Statement: [Umrah, jurisprudenceDiscussedIn, Islamic fiqh]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: jurisprudenceDiscussedIn Context triple: [Umrah, jurisprudenceDiscussedIn, Islamic fiqh]
-
A.
lawJournal
Indicates a relationship where a work is published in, associated with, or appears within a specific law journal.
-
B.
legalDoctrine
Indicates that one legal principle, rule, or theory is being applied, referenced, or relied upon as an authoritative basis for interpreting or deciding a legal issue.
-
C.
lawReview
Indicates a relationship where an entity is associated with a law review, typically as its subject, source, or venue of publication within legal scholarship.
-
D.
legalDoctrineInfluenced
Indicates that one legal doctrine has shaped, informed, or contributed to the development or interpretation of another legal doctrine.
-
E.
titleJurisdiction
Indicates the legal or official authority under which a title is recognized, governed, or issued.
- F. None of above. chosen
Provenance (4 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_69a496d6682881909ba658f1c1e0e2b0 |
completed | March 1, 2026, 7:43 p.m. |
| NER | Named-entity recognition | batch_69a4c3bb3a9c81909db2ad91defd87b6 |
completed | March 1, 2026, 10:54 p.m. |
| PD | Predicate disambiguation | batch_69a4bee64d908190b6a9bb479959d523 |
completed | March 1, 2026, 10:34 p.m. |
| PDg | Predicate description generation | batch_69a4c3b9ebdc819098de4d3288201bc1 |
completed | March 1, 2026, 10:54 p.m. |
Created at: March 1, 2026, 7:51 p.m.