Triple
T9365055
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pursuit to Mons |
E225378
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | First World War campaign |
C20682
|
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: First World War campaign Context triple: [Pursuit to Mons, instanceOf, First World War campaign]
-
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 military operation
chosen
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.
-
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 site
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.
-
E.
aspect of World War I
An aspect of World War I is a distinct thematic element—such as military strategy, technological innovation, political diplomacy, social impact, or cultural memory—that characterizes and helps explain the nature and consequences of the conflict.
- 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_69ca842cbddc819099d71ecec48cf9e5 |
completed | March 30, 2026, 2:09 p.m. |
Created at: March 30, 2026, 7:43 p.m.