Triple
T5013264
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | King Hussein Bin Talal Mosque |
E112677
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Islamic architectural landmark |
C16802
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: Islamic architectural landmark Context triple: [King Hussein Bin Talal Mosque, instanceOf, Islamic architectural landmark]
-
A.
Islamic architectural element
An Islamic architectural element is a distinct structural or decorative feature—such as arches, domes, minarets, muqarnas, or geometric and calligraphic ornamentation—that reflects the religious, cultural, and aesthetic principles of Islamic design.
-
B.
Islamic holy site
An Islamic holy site is a place of religious significance in Islam, revered for its association with Allah, the Prophet Muhammad, or key events and figures in Islamic history, and used for worship, pilgrimage, and spiritual reflection.
-
C.
Islamic centre
An Islamic centre is a community facility that serves as a hub for religious worship, education, social services, and cultural activities for Muslims.
-
D.
Islamic institution
An Islamic institution is an organized body or establishment that operates according to Islamic principles and law to provide religious, educational, social, or charitable services to the Muslim community.
-
E.
Islamic religious relic
An Islamic religious relic is a revered physical object, site, or artifact associated with the Prophet Muhammad, his companions, or significant events in Islamic history, believed to embody spiritual significance and inspire devotion among believers.
- F. None of above. chosen
Provenance (1 batch)
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_69bd4434acb8819086679dbeccc2fe54 |
completed | March 20, 2026, 12:57 p.m. |
Created at: March 20, 2026, 1:35 p.m.