Triple
T6726478
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Al Saleh Mosque |
E153529
|
entity |
| Predicate | hasSeparatePrayerAreaForWomen |
P42773
|
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 Saleh Mosque, hasSeparatePrayerAreaForWomen, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSeparatePrayerAreaForWomen Context triple: [Al Saleh Mosque, hasSeparatePrayerAreaForWomen, yes]
-
A.
canBePrayedInCongregation
Indicates that the action or ritual can be performed collectively as a group worship or prayer, rather than only individually.
-
B.
prayerHallCapacity
Indicates the maximum number of people that the prayer hall is designed or allowed to accommodate at one time.
-
C.
mainPrayerHallType
Indicates the specific architectural or functional type assigned to a main prayer hall within a religious or worship-related structure.
-
D.
hasMosque
Indicates that one entity possesses, contains, or is the location of a mosque.
-
E.
hasWorshipSpaceFeature
chosen
Indicates that a worship space possesses or includes a particular feature, characteristic, or facility.
- 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_69c6880afb988190ad88011b48ecfcba |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d354177481908ab3cf5437c095e2 |
completed | March 27, 2026, 6:58 p.m. |
| PD | Predicate disambiguation | batch_69c6d08e8a2c8190ae4e8d8c039be7ce |
completed | March 27, 2026, 6:46 p.m. |
Created at: March 27, 2026, 2:08 p.m.