Triple
T20453707
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anthony Proctor |
E501719
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | undercover officer |
C10057
|
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: undercover officer Context triple: [Anthony Proctor, instanceOf, undercover officer]
-
A.
criminal operative
A criminal operative is an individual who covertly plans, coordinates, or executes illegal activities—often within an organized network—while employing specialized skills to evade detection and law enforcement.
-
B.
police officer
chosen
A police officer is a law enforcement professional responsible for maintaining public order, preventing and investigating crimes, and protecting the safety and rights of individuals within a community.
-
C.
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.
-
D.
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.
-
E.
Kansas Bureau of Investigation agent
A Kansas Bureau of Investigation agent is a state-level law enforcement officer responsible for conducting criminal investigations, gathering and analyzing evidence, and supporting local agencies to uphold public safety and enforce Kansas laws.
- 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_69e0b4ac0a1c81908845d0f8a56abce8 |
completed | April 16, 2026, 10:06 a.m. |
Created at: April 16, 2026, 11:32 a.m.