Triple
T5665180
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Libro de Ordenanza de los toques militares de la Infantería Española |
E124841
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | reglamento militar |
C7943
|
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: reglamento militar Context triple: [Libro de Ordenanza de los toques militares de la Infantería Española, instanceOf, reglamento militar]
-
A.
military regulations
chosen
Military regulations are formal, authoritative rules and directives that govern the conduct, organization, procedures, and responsibilities of armed forces personnel and operations.
-
B.
military uniform regulation
Military uniform regulation is a set of formal rules and standards that govern the design, wear, appearance, and proper use of military uniforms and related insignia.
-
C.
military system
A military system is an organized structure of personnel, equipment, doctrines, and processes designed to plan, conduct, and support defense and combat operations.
-
D.
military administration
Military administration is the organizational and managerial framework responsible for planning, directing, and overseeing the personnel, resources, logistics, and policies that enable a military force to function effectively.
-
E.
United States Army regulation
A United States Army regulation is an official, binding directive issued by the Department of the Army that prescribes policies, responsibilities, and procedures governing the organization, operations, and conduct of Army personnel and activities.
- 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_69c00828906881908966f270b8f130cf |
completed | March 22, 2026, 3:18 p.m. |
Created at: March 22, 2026, 3:43 p.m.