Triple

T26453504
Position Surface form Disambiguated ID Type / Status
Subject Cisco TelePresence Content Server E665418 entity
Predicate vendorSupportStatus P160766 FINISHED
Object end-of-sale 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: end-of-sale | Statement: [Cisco TelePresence Content Server, vendorSupportStatus, end-of-sale]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: vendorSupportStatus
Context triple: [Cisco TelePresence Content Server, vendorSupportStatus, end-of-sale]
  • A. isSupportedBy
    Indicates that an entity is upheld, sustained, or enabled by another entity, which provides necessary assistance, resources, or justification.
  • B. supportedIn
    Indicates that one entity is valid, applicable, or functionally enabled within the context, environment, platform, or scope defined by another entity.
  • C. supportsVendor
    Indicates that one entity provides assistance, resources, or endorsement to a vendor in carrying out its activities or services.
  • D. supportsHardwareVendor
    Indicates that one entity provides assistance, resources, or endorsement to a hardware vendor in fulfilling its products or services.
  • E. tieneSoporte
    Indicates that one entity provides support, backing, or a supporting structure for another entity.
  • F. None of above. chosen

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_69ee883d5040819097dd154643005230 completed April 26, 2026, 9:48 p.m.
NER Named-entity recognition batch_69f61266f0e88190aea95f89ba2bef5c completed May 2, 2026, 3:04 p.m.
PD Predicate disambiguation batch_69f602d5c8808190a1fdbebd6f0981e8 completed May 2, 2026, 1:57 p.m.
PDg Predicate description generation batch_69f604120e848190b516c29b781d19cc completed May 2, 2026, 2:02 p.m.
Created at: April 27, 2026, 12:07 a.m.