Triple
T19759989
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bagration fleches area |
E474601
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | sector of the Borodino battlefield |
C33027
|
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: sector of the Borodino battlefield Context triple: [Bagration fleches area, instanceOf, sector of the Borodino battlefield]
-
A.
Cossack territory
Cossack territory is a semi-autonomous frontier region historically inhabited and governed by Cossack communities, characterized by military service, self-rule, and a distinct cultural identity within larger empires.
-
B.
Eastern Front sector
chosen
An Eastern Front sector is a defined geographic portion of the Eastern Front where military forces conduct coordinated operations, defense, and logistics within a larger theater of war.
-
C.
Red Army command position
A Red Army command position is an organizational role within the Soviet military hierarchy responsible for planning, directing, and controlling the operations and administration of assigned units or formations.
-
D.
Lavra
A lavra is a type of Eastern Christian monastic settlement consisting of a cluster of hermit dwellings centered around a common church and occasionally shared facilities, allowing monks to live semi-eremitical lives within a loose communal structure.
-
E.
Soviet field army
A Soviet field army was a large, operational-level military formation of the Soviet Armed Forces, typically comprising multiple corps or divisions, support units, and command structures, organized to conduct sustained offensive or defensive campaigns in a designated theater of operations.
- 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_69d8e51940a0819087bd2996f98da668 |
completed | April 10, 2026, 11:55 a.m. |
Created at: April 10, 2026, 1:48 p.m.