Triple
T30127851
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lochnagar Crater memorial site |
E765749
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | First World War battlefield site |
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: First World War battlefield site Context triple: [Lochnagar Crater memorial site, instanceOf, First World War battlefield site]
-
A.
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.
-
B.
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.
-
C.
World War I memorial
A World War I memorial is a monument or structure dedicated to commemorating the individuals and events associated with World War I, honoring the sacrifices and preserving the memory of those who served and suffered during the conflict.
-
D.
World War II site
A World War II site is a historically significant location directly associated with events, operations, or impacts of the Second World War, preserved or recognized for its cultural, military, or memorial value.
-
E.
historic battlefield
A historic battlefield is a geographically defined site where significant military engagements occurred, preserved or recognized for its cultural, educational, and commemorative value.
- 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_69f22477d1a081908df2b7e6ed16859d |
completed | April 29, 2026, 3:32 p.m. |
Created at: April 29, 2026, 7:14 p.m.