Triple
T15830463
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Queen’s Division |
E383854
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | infantry division (administrative) |
C13035
|
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: infantry division (administrative) Context triple: [Queen’s Division, instanceOf, infantry division (administrative)]
-
A.
military administrative division
chosen
A military administrative division is a geographically defined area organized under a specific command structure to manage, coordinate, and support military operations, logistics, and governance within its boundaries.
-
B.
armored infantry division
An armored infantry division is a large, combined-arms military formation that integrates mechanized infantry, tanks, artillery, and support units to conduct sustained offensive and defensive ground operations.
-
C.
airborne infantry division
An airborne infantry division is a large military formation of specially trained soldiers equipped and organized to deploy rapidly by air, typically via parachute or air assault, to seize and hold key objectives behind enemy lines.
-
D.
Wehrmacht infantry division
A Wehrmacht infantry division was a World War II-era German Army formation composed primarily of foot soldiers, supported by artillery, engineers, and logistical units, organized for sustained ground combat operations.
-
E.
Italian Army infantry division
An Italian Army infantry division is a large, combined-arms military formation primarily composed of infantry units, supported by artillery, engineers, logistics, and command elements, organized to conduct sustained ground combat 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_69d86da34c888190976e06c4019d415a |
completed | April 10, 2026, 3:25 a.m. |
Created at: April 10, 2026, 4:49 a.m.