Triple

T23683990
Position Surface form Disambiguated ID Type / Status
Subject Al-Qasr E585111 entity
Predicate instanceOf P0 FINISHED
Object medieval Islamic settlement C4488 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: medieval Islamic settlement
Context triple: [Al-Qasr, instanceOf, medieval Islamic settlement]
  • A. medieval Muslim principality
    A medieval Muslim principality is a small, semi-independent political territory ruled by a Muslim prince or governor, typically owing nominal allegiance to a larger empire or caliphate while exercising local authority over military, legal, and economic affairs.
  • B. settlement in al-Andalus
    A settlement in al-Andalus is a populated place—such as a town, village, or city—located within the historical Muslim-ruled territories of the Iberian Peninsula between the 8th and 15th centuries.
  • C. historical settlement chosen
    A historical settlement is a once-inhabited place of past human residence whose physical remains, records, and cultural traces provide evidence of earlier social, economic, and political life.
  • D. medieval city
    A medieval city is a densely populated, fortified urban center characterized by narrow winding streets, defensive walls, a central marketplace, religious and administrative buildings, and distinct social and economic quarters.
  • E. Abbasid architecture
    Abbasid architecture is the style of Islamic building that flourished under the Abbasid Caliphate (8th–13th centuries), characterized by vast brick mosques and palaces, hypostyle halls, stucco and carved brick decoration, and the development of monumental urban complexes such as Samarra.
  • 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_69e24901f7c08190909fd727632e823d completed April 17, 2026, 2:51 p.m.
Created at: April 17, 2026, 6:52 p.m.