Triple
T29870705
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spider-Verse suit |
E758586
|
entity |
| Predicate | animationEffectName |
P96809
|
FINISHED |
| Object | Vibe the Verse |
—
|
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: Vibe the Verse | Statement: [Spider-Verse suit, animationEffectName, Vibe the Verse]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: animationEffectName Context triple: [Spider-Verse suit, animationEffectName, Vibe the Verse]
-
A.
visualEffect
Indicates that one entity produces, modifies, or is associated with a particular visual effect on another entity or within a scene.
-
B.
showsEffect
Indicates that one entity produces, demonstrates, or reveals a particular effect or outcome on another entity or context.
-
C.
arrowEffect
Indicates that one entity causes or produces a directional influence or outcome on another, similar to an arrow showing the effect from source to target.
-
D.
featuresAnimation
chosen
Indicates that something includes or prominently presents an animation as part of its content or functionality.
-
E.
hasIntroEffect
Indicates that an entity produces a specific effect or outcome when it is first introduced, activated, or brought into play.
- 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_69f2245d0d7081909e37ee328542bcd7 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f676c577fc819089d5842f5edc4148 |
completed | May 2, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69f66ac32b60819092290b2de35988d3 |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 29, 2026, 5:53 p.m.