Triple
T31819950
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LeftHand Networks |
E812231
|
entity |
| Predicate | hasSuccessorProduct |
P146468
|
FINISHED |
| Object | HP StoreVirtual |
—
|
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: HP StoreVirtual | Statement: [LeftHand Networks, hasSuccessorProduct, HP StoreVirtual]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSuccessorProduct Context triple: [LeftHand Networks, hasSuccessorProduct, HP StoreVirtual]
-
A.
successorOrRelatedProduct
chosen
Indicates that one product is a successor to, replacement for, or closely related evolution of another product.
-
B.
hasModernSuccessor
Indicates that an entity is followed or replaced by another entity that serves as its modern equivalent or continuation.
-
C.
hasSuccessorShip
Indicates that one entity is the ship that follows or replaces another ship in a sequence or lineage.
-
D.
hasSuccessorUsers
Indicates that one user or set of users is followed or replaced by another user or set of users in a sequence or succession.
-
E.
hasFlagshipSuccessor
Indicates that one entity serves as the primary or leading successor to another, typically replacing it as the main or flagship version, product, or instance.
- 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_69f348e97fa48190aa06286962af6dee |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69feced53a7c819098ec474fb7d514b0 |
completed | May 9, 2026, 6:06 a.m. |
| PD | Predicate disambiguation | batch_69fecd9cd5288190aac8b4e04a7ee78e |
completed | May 9, 2026, 6:01 a.m. |
Created at: April 30, 2026, 11:45 p.m.