Triple

T34409178
Position Surface form Disambiguated ID Type / Status
Subject Viva Plus E883205 entity
Predicate hasVersionRelation P180473 FINISHED
Object Viva
Viva is a brand or product line that serves as the core offering from which the enhanced or variant version Viva Plus is derived.
 E2100209 NE FINISHED

How this triple was built (3 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: Viva | Statement: [Viva Plus, hasVersionRelation, Viva]
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Viva
Triple: [Viva Plus, hasVersionRelation, Viva]
Generated description
Viva is a brand or product line that serves as the core offering from which the enhanced or variant version Viva Plus is derived.
PD Predicate disambiguation gpt-5-mini-2025-08-07 
Target predicate: hasVersionRelation
Context triple: [Viva Plus, hasVersionRelation, Viva]
  • A. hasVersionFor chosen
    Indicates that one entity serves as a specific version or variant tailored for another entity.
  • B. hasVersionIn
    Indicates that one entity exists as a specific version or variant within the context, format, or system represented by another entity.
  • C. belongsToVersion
    Indicates that something is associated with, or is a component of, a specific version of an entity or artifact.
  • D. hasVersionType
    Indicates that one entity is associated with a specific kind or category of version of another entity.
  • E. hasVersionStatus
    Indicates that an entity is associated with a particular version state or status within its lifecycle or revision history.
  • F. None of above.

Provenance (6 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_69f349c1f2208190a09a489bb8b2719d completed April 30, 2026, 12:23 p.m.
NER Named-entity recognition batch_69f7431c0eec81909ead443e07d75e18 completed May 3, 2026, 12:44 p.m.
NED1 Entity disambiguation (via context triple) batch_6a3729ca201c81909321de6c29c63b6f completed June 21, 2026, 12:01 a.m.
NEDg Description generation batch_6a372a47f6a88190af8922a3af8c5eba completed June 21, 2026, 12:03 a.m.
NED2 Entity disambiguation (via description) batch_6a372acf6ce48190bec089a269da1194 completed June 21, 2026, 12:05 a.m.
PD Predicate disambiguation batch_69f74143cf708190a12d487884298437 completed May 3, 2026, 12:36 p.m.
Created at: May 1, 2026, 1:59 a.m.