Triple
T15296728
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mobius M. Mobius |
E365679
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Time Variance Authority agent |
C14511
|
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: Time Variance Authority agent Context triple: [Mobius M. Mobius, instanceOf, Time Variance Authority agent]
-
A.
S.H.I.E.L.D. agent
A S.H.I.E.L.D. agent is a highly trained operative working for the Strategic Homeland Intervention, Enforcement and Logistics Division, specializing in intelligence gathering, covert operations, and defense against extraordinary threats.
-
B.
B.P.R.D. agent
A B.P.R.D. agent is a specialized operative of the Bureau for Paranormal Research and Defense trained to investigate, combat, and contain supernatural and occult threats.
-
C.
former Time Agent
chosen
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.
Cyberman leader
A Cyberman leader is the commanding figure among Cybermen who directs their collective actions, strategies, and conversions with enhanced authority and tactical intelligence.
- 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_69d85a113ee881908e297a1d38dd79fa |
completed | April 10, 2026, 2:01 a.m. |
Created at: April 10, 2026, 3:15 a.m.