Triple
T4523577
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Burning of Moscow |
E103323
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | military history event |
C2148
|
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: military history event Context triple: [Burning of Moscow, instanceOf, military history event]
-
A.
military history
chosen
Military history is the study of armed conflict across time, examining wars, battles, strategies, technologies, and their political, social, and cultural impacts on societies.
-
B.
military event
A military event is an occurrence involving organized armed forces engaging in actions such as combat, maneuvers, operations, or strategic activities within a specific time and place.
-
C.
Polish military history event
A Polish military history event is a significant occurrence involving Poland’s armed forces—such as battles, campaigns, uprisings, operations, or strategic decisions—that influenced the course of Poland’s national or military development.
-
D.
United States military history event
A United States military history event is a significant occurrence involving U.S. armed forces that influences the nation’s military development, strategy, policy, or historical trajectory.
-
E.
historical armed forces
Historical armed forces are organized military institutions from past eras, composed of soldiers, equipment, and command structures, created by states or societies to conduct warfare, defend territories, and project power.
- 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_69bd43dba59881908cf59b31df8c7ae1 |
completed | March 20, 2026, 12:55 p.m. |
Created at: March 20, 2026, 1:03 p.m.