Triple
T25577046
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Venom: The Last Dance |
E641134
|
entity |
| Predicate | hasMarvelCharacter |
P52434
|
FINISHED |
| Object | Venom |
E923342
|
NE 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: Venom | Statement: [Venom: The Last Dance, hasMarvelCharacter, Venom]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMarvelCharacter Context triple: [Venom: The Last Dance, hasMarvelCharacter, Venom]
-
A.
hasMainCharacterFrom
Indicates that a work of fiction has a main character who originates from or belongs to a specified place, group, or source.
-
B.
relationshipToMarvelUniverse
Indicates the nature or type of connection an entity has to the Marvel universe, such as affiliation, role, or relevance within that fictional setting.
-
C.
hasSuperheroMantle
Indicates that one entity holds or has assumed the superhero identity, title, or role associated with another entity.
-
D.
meetsFictionalCharacter
Indicates that one entity encounters or comes into contact with a fictional character.
-
E.
franchiseCharacter
chosen
Indicates a relationship where a character belongs to, appears in, or is part of a particular media franchise.
- F. None of above.
Provenance (4 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_69e75dc281bc819095ec04dc0c3a94d0 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f739a638748190808e7a2930dce16e |
completed | May 3, 2026, 12:03 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a10d9f03b288190a640d6b52534b55b |
completed | May 22, 2026, 10:34 p.m. |
| PD | Predicate disambiguation | batch_69f732f2dc6c8190a4e86da98cc5eb05 |
completed | May 3, 2026, 11:35 a.m. |
Created at: April 21, 2026, 4:02 p.m.