Triple
T312142
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Al-Masjid an-Nabawi |
E7629
|
entity |
| Predicate | prayerDirection |
P1101
|
FINISHED |
| Object | faces 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: faces Kaaba in Mecca | Statement: [Al-Masjid an-Nabawi, prayerDirection, faces Kaaba in Mecca]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: prayerDirection Context triple: [Al-Masjid an-Nabawi, prayerDirection, faces Kaaba in Mecca]
-
A.
positionInIslamicCalendar
Indicates the specific placement or ordering of a time point (such as a date or event) within the structure of the Islamic (Hijri) calendar.
-
B.
orientation
chosen
Indicates the relative directional alignment or facing of one entity with respect to another or to a reference frame.
-
C.
SunLocation
Indicates the spatial position or placement of the sun relative to a reference point or environment.
-
D.
religiousFunction
Indicates that one entity serves a religious role, purpose, or function in relation to another entity.
-
E.
sessionOrientation
Indicates the directional or spatial alignment relationship established between entities within a session or interaction 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_69a2e7e7af7881908890039d6be4e9b8 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ea4aa16881909b2c8404b85992df |
completed | Feb. 28, 2026, 1:14 p.m. |
| PD | Predicate disambiguation | batch_69a2e940b9e8819092b821ff17ed026b |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:07 p.m.