Triple
T26595296
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | حج القِران |
E667473
|
entity |
| Predicate | requiresSacrifice |
P181205
|
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: [حج القِران, requiresSacrifice, هدي واجب عند جمهور الفقهاء]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresSacrifice Context triple: [حج القِران, requiresSacrifice, هدي واجب عند جمهور الفقهاء]
-
A.
demandedSacrifices
Indicates that one entity required or insisted that another entity offer sacrifices, typically as a condition, tribute, or act of devotion.
-
B.
sacrifice
Indicates giving up something of value, often for the benefit, protection, or advantage of another entity or goal.
-
C.
sacrificeType
Indicates the specific kind or category of sacrifice involved in a sacrificial action or relationship.
-
D.
sacrificeAcceptedBy
Indicates that a sacrificial offering made by one entity is received and deemed acceptable by another entity.
-
E.
resultOfSacrifice
Indicates that something exists or occurs as the outcome or consequence of a sacrificial act.
- 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_69ee9cfc385081909ac9ae178030a06e |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f7675b12848190a3569cfda29c5b0e |
completed | May 3, 2026, 3:18 p.m. |
| PD | Predicate disambiguation | batch_69f762f4b59481909f70074f11825bfb |
completed | May 3, 2026, 3 p.m. |
| PDg | Predicate description generation | batch_69f76759b3c48190ad8f1b33596f98c4 |
completed | May 3, 2026, 3:18 p.m. |
Created at: April 27, 2026, 2:09 a.m.