Triple
T6502830
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | F. F. E. Yeo-Thomas |
E148932
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Special Operations Executive agent |
C20509
|
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: Special Operations Executive agent Context triple: [F. F. E. Yeo-Thomas, instanceOf, Special Operations Executive agent]
-
A.
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.
-
B.
British intelligence agency
A British intelligence agency is a government organization responsible for gathering, analyzing, and acting on information to protect the United Kingdom’s national security and interests at home and abroad.
-
C.
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.
-
D.
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.
-
E.
Confederate agent
A Confederate agent is an individual who covertly gathered intelligence, conducted sabotage, or engaged in clandestine operations in support of the Confederate States during the American Civil War.
- 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_69c687e9ad288190bae5bcac9c8ac855 |
completed | March 27, 2026, 1:36 p.m. |
Created at: March 27, 2026, 1:42 p.m.