Triple
T30715931
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | national defense mobilization system |
E782023
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | national defense system |
C12441
|
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: national defense system Context triple: [national defense mobilization system, instanceOf, national defense system]
-
A.
national security system
chosen
A national security system is an integrated framework of institutions, policies, technologies, and processes designed to protect a nation’s sovereignty, citizens, critical infrastructure, and interests from internal and external threats.
-
B.
national security infrastructure
National security infrastructure is the integrated system of physical facilities, technologies, organizations, and legal frameworks designed to protect a nation’s sovereignty, critical assets, and population from internal and external threats.
-
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.
naval defense system
A naval defense system is an integrated network of sensors, weapons, platforms, and command-and-control components designed to detect, deter, and neutralize maritime threats to ships, fleets, and coastal assets.
-
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_69f224acd24481908ed5f96f0d69b5dd |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 8:35 p.m.