Triple
T9186234
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mihrab of the Prophet |
E220465
|
entity |
| Predicate | hasQiblaDirection |
P86711
|
FINISHED |
| Object | towards Kaaba in Mecca |
—
|
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: towards Kaaba in Mecca | Statement: [Mihrab of the Prophet, hasQiblaDirection, towards Kaaba in Mecca]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasQiblaDirection Context triple: [Mihrab of the Prophet, hasQiblaDirection, towards Kaaba in Mecca]
-
A.
hasQiblaCount
Indicates the number of distinct qibla directions associated with or applicable to a given entity.
-
B.
qiblaChangedTo
Indicates that the direction of ritual prayer or religious orientation has been altered to point toward a new specified location.
-
C.
qiblaChangedFrom
Indicates that the direction of prayer (qibla) was previously oriented toward a specified location before being changed to a new direction.
-
D.
historicalQibla
Indicates the direction toward which people oriented themselves for prayer in a specific historical period or context.
-
E.
positionOnKaaba
Indicates that one entity occupies a specific location or placement on the surface or structure of the Kaaba.
- 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_69ca83e6d77c81909862b7afef56b1bf |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69ccc31a52508190a83ccd76f3aa039b |
completed | April 1, 2026, 7:02 a.m. |
| PD | Predicate disambiguation | batch_69cc66090e5881908889dc1213815626 |
completed | April 1, 2026, 12:25 a.m. |
| PDg | Predicate description generation | batch_69cc66d7bf648190b8bff5b584b84975 |
completed | April 1, 2026, 12:29 a.m. |
Created at: March 30, 2026, 7:24 p.m.