Triple
T3429801
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ultimate Software |
E72308
|
entity |
| Predicate | technologyModel |
P42785
|
FINISHED |
| Object | Multi-tenant SaaS |
—
|
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: Multi-tenant SaaS | Statement: [Ultimate Software, technologyModel, Multi-tenant SaaS]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: technologyModel Context triple: [Ultimate Software, technologyModel, Multi-tenant SaaS]
-
A.
technologyType
Indicates the specific kind or category of technology associated with an entity or relationship.
-
B.
platformModel
chosen
Indicates that one entity serves as the underlying platform or foundational model upon which the other entity is built, operates, or depends.
-
C.
technologyIncludes
Indicates that one technology encompasses, contains, or incorporates another technology as part of its components, features, or implementation.
-
D.
deviceIndicates
Indicates that a device provides a signal, status, or output that conveys information about a condition, event, or state.
-
E.
technologyUsedIn
Indicates that a particular technology is employed or applied within a specific process, product, context, or domain.
- 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_69ad85ae14308190bcbc25cfa0246c0b |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb9bd61908190a7bdd01f24334fc3 |
completed | March 8, 2026, 6:02 p.m. |
| PD | Predicate disambiguation | batch_69adadfea024819094b41a13bc004bda |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:15 p.m.