Triple
T31099199
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | الحِجْر |
E792622
|
entity |
| Predicate | sanctity |
P21134
|
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: [الحِجْر, sanctity, من أشرف بقاع المسجد الحرام]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sanctity Context triple: [الحِجْر, sanctity, من أشرف بقاع المسجد الحرام]
-
A.
sacredTo
Indicates that one entity is regarded as holy, revered, or dedicated in honor of another entity, such as a deity, person, or concept.
-
B.
consecrated
Indicates that an entity has been formally dedicated or made sacred for a religious or holy purpose.
-
C.
sacredStatus
chosen
Indicates that something holds a revered, holy, or religiously significant status within a particular belief system or tradition.
-
D.
hasSanctityComparableTo
Indicates that one entity possesses a level or quality of sanctity that is comparable to that of another entity.
-
E.
inTheSpiritOf
Indicates that one entity acts, is created, or is characterized in a manner that follows the style, principles, or intent exemplified by another entity.
- 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_69f224cf157c81909e2d2bd88c9282c3 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6a916d2e08190bafc01cba73b6469 |
completed | May 3, 2026, 1:47 a.m. |
| PD | Predicate disambiguation | batch_69f6a7548eb48190a69b60a3c6ad53b9 |
completed | May 3, 2026, 1:39 a.m. |
Created at: April 29, 2026, 9:03 p.m.