Triple
T28006616
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Muhammad’s military campaigns |
E707295
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | 7th-century military history event |
C23661
|
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: 7th-century military history event Context triple: [Muhammad’s military campaigns, instanceOf, 7th-century military history event]
-
A.
8th-century historical event
An 8th-century historical event is a significant occurrence between 700 and 799 CE that influenced the political, social, cultural, or religious development of societies during that period.
-
B.
7th-century conflict
chosen
A 7th-century conflict is a military or political struggle that occurred between 600 and 699 CE, typically involving early medieval states, empires, or tribes and shaped by the religious, cultural, and territorial dynamics of that era.
-
C.
6th-century conflict
A 6th-century conflict is a historically documented war, battle, or prolonged military-political struggle that occurred between 500 and 599 CE, involving organized groups or states and significantly impacting the societies of that era.
-
D.
5th-century event
A 5th-century event is a historically significant occurrence that took place between the years 401 and 500 CE, shaping the political, social, cultural, or religious landscape of its time.
-
E.
12th-century event
A 12th-century event is a historically significant occurrence that took place between the years 1101 and 1200, often reflecting the political, cultural, religious, or social dynamics of the medieval 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_69ef96ba350c81908230d0b501b974c4 |
completed | April 27, 2026, 5:02 p.m. |
Created at: April 27, 2026, 8:01 p.m.