Triple
T29972186
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Northern sector of the Eastern Front |
E761348
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | World War I combat zone |
C15869
|
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: World War I combat zone Context triple: [Northern sector of the Eastern Front, instanceOf, World War I combat zone]
-
A.
World War I battle
A World War I battle is a large-scale, often prolonged military engagement between opposing forces during the 1914–1918 global conflict, characterized by trench warfare, industrialized weaponry, and significant casualties.
-
B.
World War I site
chosen
A World War I site is a historically significant location directly associated with events, operations, or impacts of the First World War, such as battlefields, trenches, memorials, cemeteries, or military installations.
-
C.
World War I theater
A World War I theater is a large-scale geographic region where military operations, campaigns, and battles of the First World War were conducted under a unified strategic command.
-
D.
World War I military operation
A World War I military operation is a coordinated set of strategic and tactical actions conducted by armed forces during the First World War to achieve specific military objectives within a defined time and geographic area.
-
E.
participant in World War I
A participant in World War I is any nation, military force, or individual actively involved in the political, military, or logistical operations of the global conflict between 1914 and 1918.
- 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_69f22467626081908d5afea489590e96 |
completed | April 29, 2026, 3:31 p.m. |
Created at: April 29, 2026, 6:32 p.m.