Triple
T27062626
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Meccan period |
E685085
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | period in Islamic history |
C15789
|
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: period in Islamic history Context triple: [Meccan period, instanceOf, period in Islamic history]
-
A.
era of Islamic history
chosen
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.
-
B.
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.
-
C.
Islamic historical entity
An Islamic historical entity is any person, group, institution, event, or polity significantly associated with the development, practice, or influence of Islam across history.
-
D.
Islamic historical concept
An Islamic historical concept is an idea, practice, institution, or event rooted in the development of Muslim societies over time, shaped by Islamic beliefs, law, culture, and interactions with other civilizations.
-
E.
battle of early Islamic period
A battle of the early Islamic period is a military conflict occurring during the formative decades of Islam (7th–early 8th century), typically involving Muslim forces and their regional opponents, which shaped the political, religious, and territorial foundations of the emerging Islamic world.
- 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_69ef14835fcc81908bd737b4267ae528 |
completed | April 27, 2026, 7:47 a.m. |
Created at: April 27, 2026, 8:22 a.m.