Triple
T27811708
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spider-Bots |
E702534
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Marvel universe object |
C24367
|
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: Marvel universe object Context triple: [Spider-Bots, instanceOf, Marvel universe object]
-
A.
Marvel Comics object
A Marvel Comics object is any tangible or intangible item, artifact, device, or construct that exists within the Marvel universe and plays a role in its stories, such as weapons, costumes, technology, or mystical relics.
-
B.
Marvel Cinematic Universe organization
A Marvel Cinematic Universe organization is a structured group or agency within the MCU, composed of characters united by a common purpose, hierarchy, and resources that influence the franchise’s overarching narrative and events.
-
C.
Marvel Comics objects
chosen
Marvel Comics objects are tangible or intangible items within the Marvel universe—such as weapons, artifacts, technologies, or mystical relics—that possess distinctive properties, origins, and narrative significance.
-
D.
superhero universe
A superhero universe is a fictional setting where individuals with extraordinary abilities, advanced technology, or mystical powers interact within a shared world shaped by their conflicts, alliances, and impact on society.
-
E.
location in the Marvel Cinematic Universe
A location in the Marvel Cinematic Universe is any distinct place—real or fictional—where events, characters, or organizations appear or operate within the interconnected MCU narrative.
- 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_69ef840a16748190926719ab96120bae |
completed | April 27, 2026, 3:43 p.m. |
Created at: April 27, 2026, 5:43 p.m.