Triple
T9946548
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trucking Security Program |
E195218
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | federal security program |
C357
|
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: federal security program Context triple: [Trucking Security Program, instanceOf, federal security program]
-
A.
federal government program
chosen
A federal government program is an organized set of activities, services, or regulations funded and administered by the national government to achieve specific public policy goals.
-
B.
Diplomatic Security Service program
A Diplomatic Security Service program is an organized set of policies, resources, and operations designed to protect diplomatic personnel, facilities, and information while supporting secure international engagement.
-
C.
national security law program
A national security law program is an academic or training course of study that focuses on the legal frameworks, institutions, and policies governing a nation’s defense, intelligence, and security operations.
-
D.
national security system
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.
-
E.
U.S. government security
U.S. government security is a debt instrument issued by the United States federal government, such as Treasury bills, notes, and bonds, used to finance government operations and manage national debt while providing investors with relatively low-risk returns.
- 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_69ca82e96a108190932bd1fc4acd73a0 |
completed | March 30, 2026, 2:04 p.m. |
Created at: March 30, 2026, 8:45 p.m.