Triple
T20406465
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Abdul-Karim Haeri Yazdi |
E500478
|
entity |
| Predicate | typeOfJurist |
P140026
|
FINISHED |
| Object | mujtahid |
—
|
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: mujtahid | Statement: [Abdul-Karim Haeri Yazdi, typeOfJurist, mujtahid]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfJurist Context triple: [Abdul-Karim Haeri Yazdi, typeOfJurist, mujtahid]
-
A.
legalProfessionType
Indicates the specific category or type of legal profession associated with an entity (such as lawyer, judge, or notary).
-
B.
legalProfessionRole
Indicates that one entity holds or performs a specific professional role within the legal domain in relation to another entity or context.
-
C.
legalProfessionIncludes
Indicates that a legal profession or role encompasses, involves, or includes another specified legal function, specialization, or activity.
-
D.
hasJuristHolder
Indicates that a legal or judicial role, office, or responsibility is held or occupied by a particular jurist or legal authority.
-
E.
legalProfessionTypeRegulated
Indicates that the specified type of legal profession is subject to formal regulation or oversight by an authority.
- 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_69e0b4a81bec8190b69adfdc1336a015 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e67992cfb88190ae49a1723e6667a1 |
completed | April 20, 2026, 7:08 p.m. |
| PD | Predicate disambiguation | batch_69e5765d7cb48190adec18d6d1e3d263 |
completed | April 20, 2026, 12:42 a.m. |
| PDg | Predicate description generation | batch_69e58d7481508190a87c8b88f9df9879 |
completed | April 20, 2026, 2:20 a.m. |
Created at: April 16, 2026, 11:29 a.m.