Triple
T26595277
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | حج القِران |
E667473
|
entity |
| Predicate | sharesRitesWith |
P183091
|
FINISHED |
| Object | حج الإفراد في أعمال يوم عرفة ومزدلفة ومنى |
—
|
NE NERFINISHED |
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: [حج القِران, sharesRitesWith, حج الإفراد في أعمال يوم عرفة ومزدلفة ومنى]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sharesRitesWith Context triple: [حج القِران, sharesRitesWith, حج الإفراد في أعمال يوم عرفة ومزدلفة ومنى]
-
A.
sharesElementsWith
Indicates that two entities have one or more elements or components in common.
-
B.
sharesWith
Indicates that one entity gives another entity access to or use of something it possesses.
-
C.
sharesFateWith
Indicates that two or more entities are bound to experience the same outcome, destiny, or consequences.
-
D.
sharesValuesWith
Indicates that two entities hold similar or compatible beliefs, principles, or priorities.
-
E.
sharesUniverseWith
Indicates that two entities exist within the same fictional or narrative universe, implying shared continuity, setting, or canon.
- 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_69f798387ea481909f51303f53a22e52 |
completed | May 3, 2026, 6:47 p.m. |
| PD | Predicate disambiguation | batch_69f7961550f88190b7bb8a9155458b54 |
completed | May 3, 2026, 6:38 p.m. |
| PDg | Predicate description generation | batch_69f79798663481908d6bc48dd6a94ca6 |
completed | May 3, 2026, 6:44 p.m. |
Created at: April 27, 2026, 2:09 a.m.