Triple
T24294790
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Qibla (toward the Kaaba) |
E605927
|
entity |
| Predicate | directionFromWestOfMecca |
P86711
|
FINISHED |
| Object | generally east |
—
|
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: generally east | Statement: [Qibla (toward the Kaaba), directionFromWestOfMecca, generally east]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: directionFromWestOfMecca Context triple: [Qibla (toward the Kaaba), directionFromWestOfMecca, generally east]
-
A.
hasQiblaDirection
chosen
Indicates the directional relationship specifying which way one should face (toward the Kaaba in Mecca) for prayer.
-
B.
positionOnKaaba
Indicates that one entity occupies a specific location or placement on the surface or structure of the Kaaba.
-
C.
directionFromJerusalem
Indicates the cardinal or relative compass direction of one place or object as measured outward starting from Jerusalem.
-
D.
distanceFromKaaba
Indicates the spatial distance between an entity’s location and the Kaaba.
-
E.
directionFromEarth
Indicates the compass or spatial direction in which an entity is located as observed from Earth.
- 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_69e29549335881909cbf27adcaba1cf0 |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f291593c0881908a6827f0d8899fe6 |
completed | April 29, 2026, 11:16 p.m. |
| PD | Predicate disambiguation | batch_69f1c45c6ec081908401b69424428100 |
completed | April 29, 2026, 8:42 a.m. |
Created at: April 18, 2026, 12:09 a.m.