Triple
T2101359
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | First siege of Rome by Alaric (408) |
E37099
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | event in late antiquity |
C1434
|
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 late antiquity Context triple: [First siege of Rome by Alaric (408), instanceOf, event in late antiquity]
-
A.
5th-century event
chosen
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
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.
Roman imperial persecution
Roman imperial persecution refers to the episodic, state-sanctioned suppression, punishment, and coercion of religious or political groups—most notably Christians—by Roman authorities, driven by concerns over public order, imperial unity, and traditional religious norms.
-
D.
ancient empire
An ancient empire is a large, centralized civilization from antiquity that exerts political, military, economic, and cultural control over diverse territories and peoples under a single dominant authority.
-
E.
New Testament event
A New Testament event is a significant occurrence or episode described in the New Testament writings that contributes to the narrative, theology, or historical context of early Christianity.
- 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_69a8861828948190924aa30c08806b3a |
completed | March 4, 2026, 7:20 p.m. |
Created at: March 4, 2026, 7:43 p.m.