Triple
T22992393
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Al-Hakim Mosque |
E572085
|
entity |
| Predicate | hasQiblaWall |
P150550
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Al-Hakim Mosque, hasQiblaWall, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasQiblaWall Context triple: [Al-Hakim Mosque, hasQiblaWall, yes]
-
A.
hasQiblaDirection
Indicates the directional relationship specifying which way one should face (toward the Kaaba in Mecca) for prayer.
-
B.
hasQiblaCount
Indicates the number of distinct qibla directions associated with or applicable to a given entity.
-
C.
qiblaChangedTo
Indicates that the direction of ritual prayer or religious orientation has been altered to point toward a new specified location.
-
D.
qiblihFor
Indicates a directional or locational relationship specifying that something is oriented toward, aligned with, or designated for a particular qiblih (direction of prayer).
-
E.
qiblaChangedFrom
Indicates that the direction of prayer (qibla) was previously oriented toward a specified location before being changed to a new direction.
- 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_69e245b535808190adef8a9df3c584db |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f182f017a88190b02d0649a3af5d99 |
completed | April 29, 2026, 4:02 a.m. |
| PD | Predicate disambiguation | batch_69ef3b974e7c8190b8be11dbb4518693 |
completed | April 27, 2026, 10:33 a.m. |
| PDg | Predicate description generation | batch_69ef538b29c081908fa56ee35a1dcee7 |
completed | April 27, 2026, 12:16 p.m. |
Created at: April 17, 2026, 3:50 p.m.