Triple
T12783925
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | British Army order of battle in Normandy |
E305575
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historical military document |
C1917
|
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: historical military document Context triple: [British Army order of battle in Normandy, instanceOf, historical military document]
-
A.
historical political document
A historical political document is an official or influential written record produced in a past political context that reflects, shapes, or codifies governmental decisions, ideologies, or power relations of its time.
-
B.
official military record
chosen
An official military record is an authoritative, formally maintained document or collection of documents that chronicle an individual’s or unit’s service, actions, status, and history within the armed forces.
-
C.
military planning document
A military planning document is a formal written plan that outlines objectives, strategies, resources, timelines, and contingencies for conducting military operations or activities.
-
D.
military history
Military history is the study of armed conflict across time, examining wars, battles, strategies, technologies, and their political, social, and cultural impacts on societies.
-
E.
World War II document
A World War II document is an original or reproduced written, printed, or recorded artifact created during or directly concerning the events, policies, operations, or experiences of the Second World War.
- 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_69d7bdf2b43c819098ae5aa68e61ea58 |
completed | April 9, 2026, 2:55 p.m. |
Created at: April 9, 2026, 5:29 p.m.