Triple
T3451915
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gainsight |
E72810
|
entity |
| Predicate | softwareDeliveryModel |
P9405
|
FINISHED |
| Object | cloud-based |
—
|
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: cloud-based | Statement: [Gainsight, softwareDeliveryModel, cloud-based]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: softwareDeliveryModel Context triple: [Gainsight, softwareDeliveryModel, cloud-based]
-
A.
deploymentModel
chosen
Indicates the type or manner in which a system, service, or resource is deployed or made available (e.g., on-premises, cloud, hybrid).
-
B.
softwareModel
Indicates that one entity serves as a software-based representation or abstraction (a model) of another entity or system.
-
C.
softwareProductLine
Indicates a relationship where a software product belongs to, or is part of, a broader software product line or family.
-
D.
computingModel
Indicates the computational framework, paradigm, or formal system used to perform or describe a computation.
-
E.
softwareDomain
Indicates that something belongs to, operates within, or is associated with a particular area or field of software.
- 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_69ad85b12a908190a1d10a6b03b4f8ae |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adba7465248190947f9096e230e1c4 |
completed | March 8, 2026, 6:05 p.m. |
| PD | Predicate disambiguation | batch_69adae0255b48190a9069f7871c7a012 |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:16 p.m.