Triple
T28354030
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Remington Arms (contract) |
E718175
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | military procurement agreement |
C12135
|
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: military procurement agreement Context triple: [Remington Arms (contract), instanceOf, military procurement agreement]
-
A.
military procurement programme
A military procurement programme is an organized, often long-term government initiative to identify, acquire, and manage the development, purchase, and deployment of equipment, systems, and services for the armed forces.
-
B.
bilateral military agreement
A bilateral military agreement is a formal pact between two states that outlines mutual defense commitments, security cooperation, and related military obligations and activities.
-
C.
military base agreement
A military base agreement is a formal arrangement between a host nation and a foreign state that defines the rights, responsibilities, and conditions under which the foreign state may establish, operate, and maintain military facilities on the host nation’s territory.
-
D.
government procurement agreement
chosen
A government procurement agreement is a formal arrangement that sets rules and commitments for how public authorities purchase goods, services, and works, typically to ensure transparency, fairness, and non-discrimination among suppliers.
-
E.
military rearmament program
A military rearmament program is a coordinated, government-directed initiative to expand, modernize, or restore a nation’s armed forces and weaponry in response to strategic, political, or security objectives.
- 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_69eff6ec27b481908c8d7b86c47893d9 |
completed | April 27, 2026, 11:53 p.m. |
Created at: April 28, 2026, 12:48 a.m.