Triple
T6852650
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sahnun |
E158058
|
entity |
| Predicate | jurisprudence |
P28367
|
FINISHED |
| Object | 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: fiqh | Statement: [Sahnun, jurisprudence, fiqh]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: jurisprudence Context triple: [Sahnun, jurisprudence, fiqh]
-
A.
legalPhilosophy
Indicates the philosophical principles, theories, or viewpoints that underpin or guide a legal system, doctrine, or interpretation.
-
B.
law
Indicates that one entity establishes, embodies, or enforces a rule or system of rules governing the behavior or relations of another entity.
-
C.
jurisprudenceDiscussedIn
chosen
Indicates that a topic, issue, or principle of jurisprudence is examined, analyzed, or debated within a particular document, discussion, or source.
-
D.
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.
-
E.
lawJournal
Indicates a relationship where a work is published in, associated with, or appears within a specific law journal.
- 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_69c6882fae988190864cbba788c5ebb4 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d84fffbc8190943ca7f3f03937e9 |
completed | March 27, 2026, 7:19 p.m. |
| PD | Predicate disambiguation | batch_69c6d0a12834819097d7e6c0b823745e |
completed | March 27, 2026, 6:46 p.m. |
Created at: March 27, 2026, 2:20 p.m.