Triple
T16781695
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Future Surface Combatant programme |
E407871
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | naval procurement programme |
C27756
|
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: naval procurement programme Context triple: [Future Surface Combatant programme, instanceOf, naval procurement programme]
-
A.
naval shipbuilding program
chosen
A naval shipbuilding program is an organized, long-term initiative to design, construct, and deliver warships and support vessels to meet a navy’s strategic, operational, and technological requirements.
-
B.
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.
-
C.
maritime patrol aircraft program
A maritime patrol aircraft program is an organized effort to design, acquire, operate, and sustain aircraft and supporting systems dedicated to long-range surveillance, anti-submarine warfare, and protection of maritime domains.
-
D.
naval arsenal
A naval arsenal is a specialized military facility where warships are built, repaired, equipped, and supplied with weapons, ammunition, and other naval stores.
-
E.
U.S. Navy program
A U.S. Navy program is an organized, formally managed initiative that develops, acquires, sustains, or improves naval capabilities, systems, or operations to support the Navy’s strategic and operational 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_69d8839270588190886720d9519bbf8f |
completed | April 10, 2026, 4:58 a.m. |
Created at: April 10, 2026, 5:22 a.m.