Triple
T5995669
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saadian Tombs |
E133461
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Islamic funerary complex |
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 funerary complex Context triple: [Saadian Tombs, instanceOf, Islamic funerary complex]
-
A.
Islamic architectural landmark
chosen
An Islamic architectural landmark is a prominent structure or complex that exemplifies Islamic design principles, decorative arts, and religious or cultural significance, often featuring elements such as domes, minarets, arches, and intricate geometric or calligraphic ornamentation.
-
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 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.
-
E.
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.
- F. None of above.
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_69c00870ddbc81909880fa3864f4f38d |
completed | March 22, 2026, 3:19 p.m. |
Created at: March 22, 2026, 4:05 p.m.