Triple
T26595338
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Qarin |
E667474
|
entity |
| Predicate | legalRulingVariesBy |
P39644
|
FINISHED |
| Object | madhhab |
—
|
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: madhhab | Statement: [Qarin, legalRulingVariesBy, madhhab]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: legalRulingVariesBy Context triple: [Qarin, legalRulingVariesBy, madhhab]
-
A.
legalRulingNature
Indicates the type or character of a legal ruling, such as its form, basis, or procedural nature.
-
B.
legalProtectionJurisdiction
Indicates the jurisdiction or legal authority under which an entity is granted legal protection.
-
C.
legalStatusVariesBy
chosen
Indicates that the legal status of something differs depending on a specified jurisdiction, context, or set of conditions.
-
D.
legalJurisdiction
Indicates the legal authority or geographic area whose laws and courts have the power to govern, regulate, or adjudicate matters involving the related entities.
-
E.
legalOrigin
Indicates the foundational legal system or jurisdiction from which an entity’s laws, regulations, or legal framework are derived.
- 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_69ee9cfc385081909ac9ae178030a06e |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f760a35b988190904e6267553ad2fe |
completed | May 3, 2026, 2:50 p.m. |
| PD | Predicate disambiguation | batch_69f75eb3d6f081908c933474eb359e3d |
completed | May 3, 2026, 2:41 p.m. |
Created at: April 27, 2026, 2:10 a.m.