Triple
T6790481
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Varien Inc. |
E155917
|
entity |
| Predicate | deploymentModelOfMainProduct |
P9405
|
FINISHED |
| Object | self-hosted |
—
|
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: self-hosted | Statement: [Varien Inc., deploymentModelOfMainProduct, self-hosted]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: deploymentModelOfMainProduct Context triple: [Varien Inc., deploymentModelOfMainProduct, self-hosted]
-
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.
developedProductType
Indicates that an entity (such as a project, activity, or organization) has resulted in or produced a specific type of product.
-
C.
deploymentType
Indicates the manner or configuration in which a system, application, or component is deployed or made operational.
-
D.
operatingModel
Indicates how an organization structures and manages its processes, resources, and governance to deliver its products or services.
-
E.
usesProductionModel
Indicates that one entity employs or relies on another entity as its primary or official production model in practice.
- 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_69c6881770fc8190972b2906390380f5 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d2acbfc0819081f2d6cebfb91765 |
completed | March 27, 2026, 6:55 p.m. |
| PD | Predicate disambiguation | batch_69c6d0979ce0819094678896da4e3169 |
completed | March 27, 2026, 6:46 p.m. |
Created at: March 27, 2026, 2:15 p.m.