Triple
T28898782
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vic Viper |
E732897
|
entity |
| Predicate | hasCameo |
P108137
|
FINISHED |
| Object | other Konami games |
—
|
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: other Konami games | Statement: [Vic Viper, hasCameo, other Konami games]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCameo Context triple: [Vic Viper, hasCameo, other Konami games]
-
A.
cameoCharacter
chosen
Indicates that one entity appears briefly or in a minor, special-guest role within the context or work associated with another entity.
-
B.
hasDirectorCameo
Indicates that the director of a work appears in a cameo role within that same work.
-
C.
impliedByCameo
Indicates that one fact, statement, or conclusion is inferred or supported by the appearance or brief involvement (a "cameo") of an entity in a context.
-
D.
hasNotablePersonAsFace
Indicates that an entity is publicly represented or symbolized by a specific notable person, such as a spokesperson, ambassador, or brand face.
-
E.
featuresPerformerCameo
Indicates that the subject includes a brief, special appearance by a performer who is not part of the main cast or lineup.
- 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_69f05b08c2008190ac426a035a2ed66d |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69fd2a215d6c8190a1a428ccaee603f1 |
completed | May 8, 2026, 12:11 a.m. |
| PD | Predicate disambiguation | batch_69fd28ef19688190bb8370f2812a43e7 |
completed | May 8, 2026, 12:06 a.m. |
Created at: April 28, 2026, 8:01 a.m.