Triple
T26062139
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Salah |
E657287
|
entity |
| Predicate | qiblaLocation |
P87802
|
FINISHED |
| Object | Kaaba in Mecca |
—
|
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: Kaaba in Mecca | Statement: [Salah, qiblaLocation, Kaaba in Mecca]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: qiblaLocation Context triple: [Salah, qiblaLocation, Kaaba in Mecca]
-
A.
hasQiblaDirection
Indicates the directional relationship specifying which way one should face (toward the Kaaba in Mecca) for prayer.
-
B.
qiblihFor
chosen
Indicates a directional or locational relationship specifying that something is oriented toward, aligned with, or designated for a particular qiblih (direction of prayer).
-
C.
positionOnKaaba
Indicates that one entity occupies a specific location or placement on the surface or structure of the Kaaba.
-
D.
qiblaChangedTo
Indicates that the direction of ritual prayer or religious orientation has been altered to point toward a new specified location.
-
E.
historicalQibla
Indicates the direction toward which people oriented themselves for prayer in a specific historical period or context.
- 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_69ee5bbd788481909e22bd7153d0c037 |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69f606941410819098a15b288273c3e1 |
completed | May 2, 2026, 2:13 p.m. |
| PD | Predicate disambiguation | batch_69f5aff889988190ad10bcf1a280f717 |
completed | May 2, 2026, 8:04 a.m. |
Created at: April 26, 2026, 7:18 p.m.