Triple
T9298948
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bond girl |
E223710
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | fictional role in James Bond franchise |
C17023
|
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: fictional role in James Bond franchise Context triple: [Bond girl, instanceOf, fictional role in James Bond franchise]
-
A.
James Bond character
chosen
A James Bond character is a fictional individual who inhabits the James Bond universe, defined by distinctive roles, traits, and relationships that support or oppose the iconic British secret agent in his espionage adventures.
-
B.
British intelligence officer
A British intelligence officer is a government agent responsible for gathering, analyzing, and acting on sensitive information to protect the United Kingdom’s national security and strategic interests.
-
C.
Special Operations Executive agent
A Special Operations Executive agent is a covert operative trained to conduct sabotage, espionage, and support for resistance movements behind enemy lines during wartime.
-
D.
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.
-
E.
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.
- 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_69ca8423edb08190bc0c91287a484768 |
completed | March 30, 2026, 2:09 p.m. |
Created at: March 30, 2026, 7:36 p.m.