Triple
T34474311
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Islamic inquisition |
E884988
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | event in Islamic history |
C51410
|
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: event in Islamic history Context triple: [Islamic inquisition, instanceOf, event in Islamic history]
-
A.
turning point in Islamic history
A turning point in Islamic history is a pivotal event or period that significantly alters the religious, political, social, or cultural trajectory of Muslim societies and reshapes the development of the Islamic world.
-
B.
Islamic religious event
An Islamic religious event is a scheduled gathering or observance rooted in Islamic beliefs and practices, such as prayers, festivals, commemorations, or educational activities, conducted according to Islamic teachings and traditions.
-
C.
era of Islamic history
An era of Islamic history is a distinct period characterized by particular political structures, cultural developments, religious thought, and social dynamics within the broader historical trajectory of Muslim societies.
-
D.
event in the Crusades movement
An event in the Crusades movement is a specific historical occurrence—such as a battle, council, treaty, or campaign—directly related to the religiously motivated military expeditions between Latin Christendom and its opponents in the medieval eastern Mediterranean and surrounding regions.
-
E.
Islamic historical entity
chosen
An Islamic historical entity is any person, group, institution, event, or polity significantly associated with the development, practice, or influence of Islam across history.
- 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_69f349c880408190ade571c471ab154a |
completed | April 30, 2026, 12:23 p.m. |
Created at: May 1, 2026, 2:01 a.m.