Triple
T2556423
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Developer Edition |
E56738
|
entity |
| Predicate | canBeInstalledOn |
P31902
|
FINISHED |
| Object | on-premises servers |
—
|
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: on-premises servers | Statement: [Developer Edition, canBeInstalledOn, on-premises servers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBeInstalledOn Context triple: [Developer Edition, canBeInstalledOn, on-premises servers]
-
A.
hasHardwareCompatibilityWith
Indicates that two hardware components or systems can operate together correctly and reliably without conflicts or incompatibilities.
-
B.
hasSoftwareCompatibilityWith
Indicates that one software system can operate correctly and effectively with another software system, without conflicts or required modifications.
-
C.
preinstalledOn
Indicates that a software or component comes already installed and ready to use on a particular device or system before the user receives it.
-
D.
installedAt
Indicates that something has been set up, placed, or put into operation at a specific location or site.
-
E.
supportsInstallation
chosen
Indicates that one entity is capable of enabling, handling, or being compatible with the installation of another entity.
- 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_69ab4a4bfec081908039988ec4c86e28 |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abd5a33234819082ad49fa6594b6be |
completed | March 7, 2026, 7:37 a.m. |
| PD | Predicate disambiguation | batch_69abd0c8b6f08190a68645db3e8b779a |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:48 p.m.