Triple
T34409181
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Viva Plus |
E883205
|
entity |
| Predicate | hasUpgradePathFrom |
P37414
|
FINISHED |
| Object | Viva core |
—
|
NE NERFINISHED |
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: Viva core | Statement: [Viva Plus, hasUpgradePathFrom, Viva core]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasUpgradePathFrom Context triple: [Viva Plus, hasUpgradePathFrom, Viva core]
-
A.
mayBeUpgradedTo
Indicates that one entity is eligible or allowed to be changed into a higher, improved, or more advanced version represented by another entity.
-
B.
hasUpgrade
Indicates that one entity possesses, includes, or is associated with an improved or enhanced version of another entity.
-
C.
hasUpgradeProject
Indicates that an entity is associated with a project whose purpose is to improve, enhance, or modernize that entity.
-
D.
upgradesFrom
chosen
Indicates that one entity is a newer or improved version that replaces or enhances another entity.
-
E.
usedInUpgradeOf
Indicates that something serves as a component, resource, or prerequisite that is utilized during the process of upgrading another entity.
- 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_69f349c1f2208190a09a489bb8b2719d |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f71c35327c8190884f1bfe12bd2cd7 |
completed | May 3, 2026, 9:58 a.m. |
| PD | Predicate disambiguation | batch_69f71822d0e88190ac9731c7ae5a4def |
completed | May 3, 2026, 9:40 a.m. |
Created at: May 1, 2026, 1:59 a.m.