Triple
T3473560
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Council of Rome (1076) |
E73318
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | 11th-century religious event |
C1474
|
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: 11th-century religious event Context triple: [Council of Rome (1076), instanceOf, 11th-century religious event]
-
A.
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.
-
B.
event in church history
chosen
An event in church history is a significant occurrence or development within the life of the Christian church that influences its doctrine, practice, structure, or relationship with society over time.
-
C.
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.
-
D.
15th-century event
A 15th-century event is a historically significant occurrence that took place between 1401 and 1500, shaped by and contributing to the political, social, cultural, or technological transformations of that period.
-
E.
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.
- 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_69ad85b2fed48190948c8765e453d270 |
completed | March 8, 2026, 2:20 p.m. |
Created at: March 8, 2026, 3:17 p.m.