Triple
T25797401
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Inglourious Basterds (commando unit) |
E649724
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | fictional commando unit |
C4374
|
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 commando unit Context triple: [Inglourious Basterds (commando unit), instanceOf, fictional commando unit]
-
A.
fictional military program
A fictional military program is an imagined, often secretive initiative or project within an armed forces setting, designed to explore advanced technologies, strategies, or operations that drive the narrative in speculative or military-themed stories.
-
B.
special operations forces unit
A special operations forces unit is a highly trained, small military team designed to conduct specialized, high-risk missions such as reconnaissance, direct action, counterterrorism, and unconventional warfare, often in politically sensitive or denied environments.
-
C.
commando engineer unit
A commando engineer unit is a specialized military formation that combines combat-trained commandos with engineering expertise to conduct rapid, high-risk construction, demolition, breaching, and sabotage operations in hostile or contested environments.
-
D.
Tal Shiar operative
A Tal Shiar operative is a covert intelligence agent of the Romulan Star Empire, specializing in espionage, political manipulation, and ruthless enforcement of state security.
-
E.
fictional group
chosen
A fictional group is an imagined collection of characters or entities, defined by shared traits, goals, or context, that exists only within a narrative or creative work.
- 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_69e7ab34f8c8819099f6c4dabdabf129 |
completed | April 21, 2026, 4:52 p.m. |
Created at: April 22, 2026, 6:32 a.m.