Triple
T7988515
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FBI Most Wanted Terrorists |
E185743
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | FBI list |
C20122
|
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 list Context triple: [FBI Most Wanted Terrorists, instanceOf, FBI list]
-
A.
most wanted list
chosen
A most wanted list is an official compilation of individuals sought by authorities, typically for serious crimes, prioritized for capture or information leading to their arrest.
-
B.
Indian agent
An Indian agent is a government-appointed official historically responsible for managing relations, negotiations, and administrative affairs between a colonial or federal authority and Indigenous or Native American tribes.
-
C.
Pinkerton detective
A Pinkerton detective is a private investigator employed by the Pinkerton National Detective Agency, historically known for security work, strikebreaking, and pursuing high-profile criminals in the United States.
-
D.
terrorist watchlisting system
A terrorist watchlisting system is a centralized platform that collects, analyzes, and shares information on individuals suspected of terrorism-related activities to support threat detection, risk assessment, and operational decision-making by authorized agencies.
-
E.
counterterrorism database
A counterterrorism database is a centralized, secure repository that stores, organizes, and enables analysis of information related to terrorist organizations, individuals, activities, and incidents to support prevention, investigation, and response efforts.
- 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_69ca829a2cfc819083d591d58ec04075 |
completed | March 30, 2026, 2:03 p.m. |
Created at: March 30, 2026, 5:16 p.m.