Triple
T3608247
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Great Fire of Rome |
E76424
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | disaster in Rome |
C223
|
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: disaster in Rome Context triple: [Great Fire of Rome, instanceOf, disaster in Rome]
-
A.
disaster
chosen
A disaster is a sudden, disruptive event—natural or human-made—that causes significant harm to people, property, or the environment and overwhelms normal coping capacities.
-
B.
sack of a city
The sack of a city is a violent military event in which invading forces seize and plunder an urban center, often accompanied by widespread destruction, looting, and atrocities against its inhabitants.
-
C.
ruin
A ruin is the remaining structure or fragments of a once-intact building or civilization, now decayed or destroyed by time, neglect, or catastrophe.
-
D.
client state of the Roman Empire
A client state of the Roman Empire was a formally independent polity that maintained its own rulers and internal administration while being bound by treaty to support Roman foreign policy, pay tribute or provide troops, and accept Roman influence over its succession and external affairs.
-
E.
end of an empire
The end of an empire is the historical moment when a once-dominant imperial power irreversibly loses its political cohesion, territorial control, and cultural authority, giving way to new states, systems, or social orders.
- 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_69ad85da0ba481908b3b48c69efe2b98 |
completed | March 8, 2026, 2:21 p.m. |
Created at: March 8, 2026, 3:22 p.m.