Triple
T4628823
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hassan II Mosque |
E101162
|
entity |
| Predicate | hasPrayerHallType |
P53929
|
FINISHED |
| Object | hypostyle hall |
—
|
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: hypostyle hall | Statement: [Hassan II Mosque, hasPrayerHallType, hypostyle hall]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrayerHallType Context triple: [Hassan II Mosque, hasPrayerHallType, hypostyle hall]
-
A.
mainPrayerHallType
chosen
Indicates the specific architectural or functional type assigned to a main prayer hall within a religious or worship-related structure.
-
B.
containsPrayerType
Indicates that one entity includes or encompasses a specific type or category of prayer.
-
C.
hasMosque
Indicates that one entity possesses, contains, or is the location of a mosque.
-
D.
prayerHallCapacity
Indicates the maximum number of people that the prayer hall is designed or allowed to accommodate at one time.
-
E.
hasMihrab
Indicates that a structure or space contains or is equipped with a mihrab, the niche indicating the direction of prayer in a mosque or Islamic prayer area.
- 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_69bd43d0497c8190ac23c65c5804846a |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd5a300e6081909fa9f504aada33ea |
completed | March 20, 2026, 2:31 p.m. |
| PD | Predicate disambiguation | batch_69bd5231db7c8190b38d4fdbad8bf842 |
completed | March 20, 2026, 1:57 p.m. |
Created at: March 20, 2026, 1:13 p.m.