Triple

T35298711
Position Surface form Disambiguated ID Type / Status
Subject Jabberwacky E1019446 entity
Predicate hasOnlineServiceType P849 FINISHED
Object software as a service 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: software as a service | Statement: [Jabberwacky, hasOnlineServiceType, software as a service]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasOnlineServiceType
Context triple: [Jabberwacky, hasOnlineServiceType, software as a service]
  • A. hasServiceType chosen
    Indicates that an entity is associated with or categorized by a particular type of service.
  • B. operatesOnlineService
    Indicates that an entity runs or manages an online service or platform for others to use.
  • C. hasServiceTo
    Indicates that one entity provides, offers, or operates a service for or directed toward another entity.
  • D. hasSupportService
    Indicates that one entity provides or is associated with a support-related service for another entity.
  • E. hasOnlineProvision
    Indicates that an entity offers or supports a service, feature, or function through an online or internet-based channel.
  • 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_69f76de7eedc8190a3bdc64ebbc05b42 completed May 3, 2026, 3:46 p.m.
NER Named-entity recognition batch_69fcd867f36081908c88c55a6a1404c1 completed May 7, 2026, 6:22 p.m.
PD Predicate disambiguation batch_69fcd1f47b188190b4cf4b4c748d9d03 completed May 7, 2026, 5:55 p.m.
Created at: May 3, 2026, 4:03 p.m.