Triple
T25759152
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FBI files on Lee Harvey Oswald |
E648689
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | FBI file |
C50760
|
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 file Context triple: [FBI files on Lee Harvey Oswald, instanceOf, FBI file]
-
A.
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.
-
B.
former FBI agent
A former FBI agent is an individual who previously served in the Federal Bureau of Investigation, typically possessing investigative, analytical, and law enforcement expertise gained from that role.
-
C.
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.
-
D.
federal government database
A federal government database is a centralized, secure digital repository used by national government agencies to store, manage, and retrieve official records, data, and information for administrative, regulatory, and public service purposes.
-
E.
federal government database
A federal government database is a centralized, electronically managed collection of structured data maintained by national government agencies to store, process, and retrieve information for administrative, regulatory, and public service purposes.
- F. None of above. chosen
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_69e7ab314d788190b3abe19e114080e1 |
completed | April 21, 2026, 4:52 p.m. |
Created at: April 22, 2026, 4:43 a.m.