Triple
T28717813
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FBI Top Echelon Informant Program |
E730009
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | FBI informant program |
C53412
|
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: FBI informant program Context triple: [FBI Top Echelon Informant Program, instanceOf, FBI informant program]
-
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.
law enforcement intelligence program
chosen
A law enforcement intelligence program is a coordinated set of processes, technologies, and policies used by agencies to collect, analyze, and share information for preventing, detecting, and investigating crime and threats.
-
C.
government informant
A government informant is an individual who secretly provides information or intelligence to a government agency about persons, organizations, or activities, often to support investigations or national security efforts.
-
D.
FBI special agent
An FBI special agent is a highly trained federal law enforcement officer responsible for investigating and enforcing U.S. federal laws, often specializing in areas such as counterterrorism, cybercrime, organized crime, or public corruption.
-
E.
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.
- 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_69f043e7d5a4819094b18aca10b1e024 |
completed | April 28, 2026, 5:21 a.m. |
Created at: April 28, 2026, 5:51 a.m.