Triple
T4073650
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | vAuto |
E86706
|
entity |
| Predicate | softwareCategory |
P37802
|
FINISHED |
| Object | 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: SaaS | Statement: [vAuto, softwareCategory, SaaS]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: softwareCategory Context triple: [vAuto, softwareCategory, SaaS]
-
A.
softwareName
Indicates that one entity is the name or title of a software application associated with another entity.
-
B.
applicationRequirement
Indicates that one entity specifies a condition or prerequisite that must be met for the use, approval, or execution of another entity or process.
-
C.
softwareIncluded
Indicates that certain software is bundled with, provided alongside, or contained within another item or offering.
-
D.
softwareDomain
chosen
Indicates that something belongs to, operates within, or is associated with a particular area or field of software.
-
E.
programUsed
Indicates that a particular program, software, or application was employed or utilized in performing an action or achieving a result.
- 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_69aed93ebe448190a1f1686e28740ac9 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefc245d888190ae773f9c3077953b |
completed | March 9, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69aef9061d2481908307cafc9e9b32c0 |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:39 p.m.