Triple
T20993815
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Union Corse |
E517092
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | organization in the James Bond universe |
C44453
|
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: organization in the James Bond universe Context triple: [Union Corse, instanceOf, organization in the James Bond universe]
-
A.
James Bond adaptation
A James Bond adaptation is a creative work that reinterprets the James Bond character, stories, or themes from Ian Fleming’s novels or the film franchise into a new medium, style, or narrative context.
-
B.
James Bond character
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.
-
C.
espionage franchise
An espionage franchise is a recurring series of related stories, often spanning films, books, games, or TV, that centers on spies, covert operations, and intelligence agencies navigating high-stakes political or criminal intrigue.
-
D.
James Bond continuation novel
A James Bond continuation novel is an officially authorized work of fiction written by an author other than Ian Fleming that extends the adventures of the James Bond character beyond the original canon.
-
E.
James Bond location
A James Bond location is a distinctive, often exotic setting—such as a city, landmark, or hidden lair—that serves as the backdrop for key espionage, action, or narrative events in the James Bond universe.
- 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_69e0b5006e2881909fc2383f841740cc |
completed | April 16, 2026, 10:08 a.m. |
Created at: April 16, 2026, 1:50 p.m.