Triple
T8433624
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shuri |
E199172
|
entity |
| Predicate | roleInInfinityWar |
P58964
|
FINISHED |
| Object | attempts to remove Mind Stone from Vision |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: attempts to remove Mind Stone from Vision | Statement: [Shuri, roleInInfinityWar, attempts to remove Mind Stone from Vision]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInInfinityWar Context triple: [Shuri, roleInInfinityWar, attempts to remove Mind Stone from Vision]
-
A.
roleInFilmEcosystem
Indicates the specific function or position an entity holds within the broader network of activities, stakeholders, and processes that make up the film ecosystem.
-
B.
hasInUniverseRole
chosen
Indicates that an entity holds or performs a specific role or function within a particular fictional or defined universe.
-
C.
roleInElysium
Indicates that an entity holds a specific role, position, or function within the context of Elysium.
-
D.
roleInNebula
Indicates that an entity holds a specific function, position, or involvement within a particular nebula.
-
E.
fictionalUniverseRole
Indicates the role or function an entity has within a particular fictional universe or narrative setting.
- F. None of above.
Provenance (3 batches)
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_69ca8313c99081909a5c6d83b91de5b3 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe30fba4081908bfdef3faf5baceb |
completed | March 31, 2026, 3:06 p.m. |
| PD | Predicate disambiguation | batch_69cbd0ec200c8190b0299e2b0b4bdcc2 |
completed | March 31, 2026, 1:49 p.m. |
Created at: March 30, 2026, 6:07 p.m.