Triple
T6521626
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | División de Operaciones |
E151195
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | división militar |
C2497
|
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: división militar Context triple: [División de Operaciones, instanceOf, división militar]
-
A.
military administrative division
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.
military unit
chosen
A military unit is an organized group of armed personnel structured under a defined command hierarchy to perform specific tactical or operational missions.
-
C.
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.
-
D.
military organization
A military organization is a structured group of armed forces personnel and resources, organized under a defined hierarchy and command system, to plan, coordinate, and conduct defense and combat operations in support of a state’s strategic objectives.
-
E.
defense organization
A defense organization is an entity, typically governmental or intergovernmental, responsible for planning, coordinating, and executing activities to protect a nation or group of nations from military and security threats.
- 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_69c687f522748190b3058405553cdabd |
completed | March 27, 2026, 1:36 p.m. |
Created at: March 27, 2026, 1:45 p.m.