Triple
T650011
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Joint Strike Fighter program |
E11324
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | multinational defense program |
C3132
|
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: multinational defense program Context triple: [Joint Strike Fighter program, instanceOf, multinational defense program]
-
A.
multinational mission mechanism
A multinational mission mechanism is a structured framework of processes, agreements, and coordinating bodies that enables multiple countries or organizations to collaboratively plan, resource, and execute a shared mission across borders.
-
B.
nuclear weapons program
A nuclear weapons program is an organized, often state-led effort to research, develop, test, produce, and maintain nuclear warheads and their delivery systems for military deterrence or potential use.
-
C.
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.
-
D.
collective defense agreement
A collective defense agreement is a formal pact among multiple states committing each to consider an attack on one member as an attack on all and to respond with coordinated defense measures.
-
E.
intergovernmental programme
chosen
An intergovernmental programme is a coordinated set of policies, activities, or initiatives jointly designed, funded, and implemented by multiple governments or international organizations to address shared issues or achieve common goals across borders.
- 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_69a493266a2881909daf4c40f719dee8 |
completed | March 1, 2026, 7:27 p.m. |
Created at: March 1, 2026, 7:36 p.m.