Triple
T31024941
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oxcart |
E790543
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | CIA codename |
C14464
|
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: CIA codename Context triple: [Oxcart, instanceOf, CIA codename]
-
A.
CIA program
A CIA program is an organized, often covert initiative or operation designed and managed by the Central Intelligence Agency to achieve specific intelligence, security, or foreign policy objectives.
-
B.
intelligence agency code number
A unique identifier assigned by an intelligence agency to classify, track, and reference specific operations, assets, documents, or personnel within its information systems.
-
C.
wartime codename
A wartime codename is a deliberately chosen, often cryptic label used to conceal the true nature, identity, or objectives of military operations, units, technologies, or locations during conflict.
-
D.
CIA front company
A CIA front company is a seemingly legitimate business entity secretly created or controlled by the Central Intelligence Agency to provide cover, funding, logistics, or operational support for intelligence activities without revealing government involvement.
-
E.
Central Intelligence Agency operation
chosen
A Central Intelligence Agency operation is a covert or clandestine activity planned, authorized, and executed by the CIA to collect intelligence, influence events, or protect U.S. national security interests, often involving secrecy, specialized tradecraft, and coordination with domestic or foreign partners.
- 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_69f224c811508190a7de096a5b1f5798 |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 8:58 p.m.