Triple
T36870983
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sallah |
E911221
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Indiana Jones character |
C66148
|
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: Indiana Jones character Context triple: [Sallah, instanceOf, Indiana Jones character]
-
A.
Indiana Jones franchise location
An Indiana Jones franchise location is any real or fictional place featured in the Indiana Jones films, television series, or related media that serves as a significant setting for the story’s archaeological adventures, discoveries, or conflicts.
-
B.
Mission: Impossible character
A Mission: Impossible character is an individual—often a highly skilled agent, ally, or adversary—whose actions, loyalties, and specialized abilities drive the intricate espionage missions and high-stakes conflicts of the Mission: Impossible universe.
-
C.
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.
-
D.
Top Gun character
A Top Gun character is a highly skilled, larger-than-life naval aviator or associated figure whose personality, relationships, and aerial combat prowess drive the drama and action within the Top Gun universe.
-
E.
Avatar franchise character
An Avatar franchise character is an individual, creature, or spirit from the Avatar universe whose identity, abilities, and relationships are shaped by the world’s elemental bending, cultures, and ongoing conflicts.
- 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_69f76e82339881909607a65c0503d941 |
completed | May 3, 2026, 3:49 p.m. |
Created at: May 3, 2026, 4:13 p.m.