Triple
T5654698
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | James D. Bulloch |
E124588
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Confederate agent |
C18526
|
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: Confederate agent Context triple: [James D. Bulloch, instanceOf, Confederate agent]
-
A.
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.
-
B.
Soviet agent
A Soviet agent is an individual who covertly gathers, transmits, or influences information and activities on behalf of the Soviet state’s intelligence or security services, often operating under false identities or clandestine arrangements.
-
C.
assassin's accomplice
An assassin's accomplice is a covert collaborator who aids a killer in planning, facilitating, or covering up targeted murders without directly carrying out the killing.
-
D.
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.
-
E.
former Time Agent
A former Time Agent is an ex-member of a temporal law enforcement organization who once policed, manipulated, or monitored timelines but has since left or been removed from that role, often carrying specialized knowledge, skills, and psychological baggage from their time-traveling past.
- 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_69c0082774a481909d7e63fb2aad56ac |
completed | March 22, 2026, 3:17 p.m. |
Created at: March 22, 2026, 3:42 p.m.